From f3fb76d5936f4d83af0d73024374ef25fc5deb2b Mon Sep 17 00:00:00 2001 From: David Anderson Date: Thu, 25 Nov 2004 07:58:14 +0000 Subject: [PATCH] *** empty log message *** svn path=/trunk/boinc/; revision=4654 --- doc/app.php | 49 +++++++++++++++++++++++++------------------------ doc/work.php | 10 +++++----- 2 files changed, 30 insertions(+), 29 deletions(-) diff --git a/doc/app.php b/doc/app.php index 06d24797cf..9011d85a7b 100644 --- a/doc/app.php +++ b/doc/app.php @@ -3,9 +3,9 @@ require_once("docutil.php"); page_head("Applications and versions"); echo "

-An application represents a particular distributed computation; -it consists of a program (perhaps with versions for different platforms) -and a set of workunits and results. +An application represents a collection of related computation. +It consists of a program (perhaps with versions for different platforms) +and a set of workunits and results. A project can operate many applications. Applications are maintained in the application table in the BOINC DB, and can be created using the xadd utility. @@ -16,15 +16,16 @@ An application program may go through a sequence of A particular version, compiled for a particular platform, is called an application version. An application version can consist of multiple files: for example, a -controller script, pre- and post-processing programs, and a primary executable. +controller script, pre- and post-processing programs, and a primary program.

Each application version has an integer version number. -Projects can assign version numbers however they like; for example, -version 304 might represent major version 3 and minor version 4. +This number is of the form 100*major + minor; +for example, 304 represents major version 3 and minor version 4. +An application version will only run on a core client +having the same major version. Version numbers should be used consistently across platforms; -Windows version 304 should be computationally identical to -Mac version 304. +Windows version 304 should be computationally identical to Mac version 304.

Each application has a minimum version. @@ -37,22 +38,22 @@ Application versions are maintained in the app_version table in the BOINC DB. Each entry includes an XML document describing the files that make up the application version: -

-<file_info> ... 
-</file_info>
-[ ... 
-]
-<app_version>
-    <app_name>foobar</app_name>
-    <version_num>4</version_num>
-    <file_ref>
-        <file_name>program_1</file_name>
-        <main_program/>
-    </file_ref>
-    <file_ref>
-        <file_name>library_12</file_name>
-    </file_ref>
-</app_version>
+
".htmlspecialchars("
+
+   ... 
+
+[ ... ]
+
+    foobar
+    4
+    
+        program_1
+        
+    
+    
+        library_12
+    
+")."
 
Application versions can be created using update_versions. diff --git a/doc/work.php b/doc/work.php index 7e037cb95a..87e45b0a37 100644 --- a/doc/work.php +++ b/doc/work.php @@ -4,7 +4,7 @@ page_head("Workunits"); echo "

A workunit describes a computation to be performed. -The basic workunit attributes include: +Its attributes include: "; list_start(); @@ -14,10 +14,10 @@ list_item( ); list_item( "application", - "Which application performs the computation. - A workunit is associated with an application, not with a particular - version or range of versions. - If the format of your input data changes in + "Which application will perform the computation. + A workunit is associated with an application, + not with a particular version or range of versions. + If the input data format changes in a way that is incompatible with older versions, you must create a new application. This can often be avoided by using XML data format. "