Changes between Version 6 and Version 7 of RemoteInputFiles

Timestamp:

Jul 22, 2016, 3:24:07 PM (8 years ago)

Author:

davea

Comment:

--

RemoteInputFiles

@@ -11 +11 @@
 so they can't store files there directly.
 Instead, BOINC provides two mechanisms that allow
-job submitters to place files on the BOINC server.
+job submitters to store and manage files on the BOINC server.
 
 Each of these mechanisms deals with several issues:
@@ -18 +18 @@
   of a given name can never be changed.
   Job submitters can't be expected to obey this rule:
-  they must be able to submit one job with an input file
-  of a given name, and a second job with an input file of
-  the same name but different contents.
+  they must be able to submit one job with an input file of a given name,
+  and a second job with an input file of the same name but different contents.
  * File cleanup: There must be some way to clean up
   files on the server when they are no longer needed.
@@ -36 +35 @@
 == Content-based file management ==
 
-In this system, the name of a file on the BOINC server
-is based on its MD5 hash; thus file immutability is automatic.
+In this system, the BOINC name of a file
+(i.e. its name on the BOINC server)
+is based on its hash; thus file immutability is automatic.
 
 File cleanup is based on file/batch associations.
@@ -57 +57 @@
     const char* project_url,
     const char* authenticator,
+    std::vector<string> &boinc_names,
     int batch_id,
-    vector<string> &md5s,
-    vector<string> &paths,
-    vector<int> &absent_files           // output
+    std::vector<int> &absent_files,             // output
+    std::string& error_message
 );
 }}}
@@ -67 +67 @@
  * '''project_url''': the project's master URL
  * '''authenticator''': the job submitter's authenticator.
- * '''paths''': a list of file paths on the calling host.
- * '''md5s''': a list of the MD5s of the files.
+ * '''boinc_names''': a list of the "BOINC names" of the files.  Must include a hash; can include a suffix if needed.
  * '''batch_id''': the ID of a batch whose jobs will reference the files
   (these jobs need not exist yet).
@@ -80 +79 @@
  * return value: nonzero on error
  * '''absent_files''': a list of files not present on the server
-  (represented as indices into the file vector).
+  (represented as indices into the boinc_names vector).
+ * '''error_message''': if error, an explanatory string.
 
 {{{
@@ -86 +86 @@
     const char* project_url,
     const char* authenticator,
-    vector<string> &paths,
-    vector<string> &md5s,
-    int batch_id
+    std::vector<string> &paths,
+    std::vector<string> &boinc_names,
+    int batch_id,
+    std::string& error_message
 );
 }}}
@@ -95 +96 @@
  * '''project_url, authenticator, batch_id''': as above.
  * '''paths''': a list of paths of files to be uploaded
- * '''md5s''': a list of MD5 hashes of these files
+ * '''boinc_names''': a list of BOINC names of these files (see above).
  * '''batch_id''': the ID of a batch with which the files are associated.
-  The operation will fail if the user is not authorized to
-  submit jobs to the batch's application.
+  The operation will fail if the user is not authorized to submit jobs to the batch's application.
 
 Action: Upload the files, and create associations to the given batch.
@@ -104 +104 @@
 Output:
  * return value: nonzero on error
+ * '''error_message''': if error, an explanatory string.
 
 If you use this system, periodically run the script
 '''html/ops/delete_job_files'''.
-This will delete files that are no longer associated
-with an active batch.
+This will delete files that are no longer associated with an active batch.
 
 == Per-user file sandbox ==