Changes between Version 13 and Version 14 of WrapperApp

Timestamp:

May 28, 2007, 8:59:30 AM (18 years ago)

Author:

davea

Comment:

--

WrapperApp

@@ -27 +27 @@
 
 The job file specifies a sequence of tasks.
-The descriptor for each task includes the name of the application.
-If the application uses standard I/O (stdin, stdout or stderr)
+The descriptor for each task includes the name of the application, or 'worker program'.
+If the worker program uses standard I/O (stdin, stdout or stderr)
 the descriptor specifies the logical names of the files
 to which these are to be connected.
-The descriptor may also specify command-line argments to be passed to the application.
+The descriptor may also specify command-line argments to be passed to the worker program.
 '''wrapper''' itself may be passed command-line arguments (specified in the workunit template);
-these are passed to each of the applications after those specified in the job file.
+these are passed to each of the worker programs after those specified in the job file.
 
 The job file can specify multiple tasks.
@@ -49 +49 @@
 == Example ==
 
-Here's an example of this mechanism:
+Here's an example that shows how to use this mechanism:
  * Compile the program 'worker' from the [ExampleApps boinc_samples] tree, producing (say) 'worker_5.10_windows_intelx86.exe'. This is the legacy app. If reads from stdin and writes to stdout; it also opens and reads a file 'in', and opens and writes a file 'out'. It takes one command-line argument: the number of CPU seconds to use.
  * Compile the program 'wrapper' from the [ExampleApps boinc_samples] tree, producing (say) 'wrapper_5.10_windows_intelx86.exe'. This program executes your legacy application, and acts as a proxy for it (to report CPU time etc.).