Changes between Version 9 and Version 10 of BoincFiles

Timestamp:

Sep 24, 2009, 4:34:05 PM (15 years ago)

Author:

davea

Comment:

--

BoincFiles

@@ -3 +3 @@
 == Files and data servers ==
 
-The BOINC storage model is based on '''files'''. Examples of files:
+The BOINC storage model is based on '''files'''.
+Examples of files:
 
     * The inputs and outputs of computation;
@@ -11 +12 @@
 The BOINC core client transfers files to and from project-operated '''data servers''' using HTTP.
 
-Files are '''immutable'''. This means that all replicas of that file are assumed (and required) to be identical. If a file is changed, even by a single byte, it becomes a new file, and must be given a different name than the original.
+A file of a given name is '''immutable'''.
+This means that all replicas of that file are assumed (and required) to be identical.
+If a file is changed, even by a single byte, it becomes a new file, and must be given a different name than the original.
 
 == File properties ==
@@ -17 +20 @@
 Files have various properties, including:
 
-    * '''Physical name:''' unique identifier for the file. Must be nonempty, at most 255 chars, and may not contain '..' or '%'.
+    * '''Physical name:''' unique identifier for the file. Must be nonempty, at most 255 chars, and may not contain '..', '/', or '%'.
     * '''Sticky:''' don't delete file on client (see below).
     * '''Report on RPC:''' include a description of this file in scheduler requests.
     * '''Maximum size:''' if an output file exceeds its maximum size, the computation is aborted. 
 
-File properties are specified in [XmlFormat#file_info XML elements] that appear, for example, in [WorkGeneration workunit templates].
+File properties are specified in [WorkGeneration job input and output templates].
 
 == File references ==