79 | | The components are: |
80 | | |
81 | | <file_info>, <file_ref>:: |
82 | | |
83 | | Each pair describes an [BoincFiles#Fileproperties output file] and [BoincFiles#Filereferences the way it's referenced]. |
84 | | |
85 | | Note: when a job is created, the name of its output template file is stored. |
| 79 | Each <file_info>, <file_ref> pair describes an output file. |
| 80 | The elements include: |
| 81 | '''<name>''' and '''<file_name>''':: the physical file name. Typically use <OUTFILE_0>, <OUTFILE_1> etc.; this will be replaced with a generated name based on the job name. |
| 82 | '''<generated_locally/>''':: always include this for output files. |
| 83 | '''<max_nbytes>''':: maximum file size. If the actual size exceeds this, the file will not be uploaded, and the job will be marked as an error. |
| 84 | '''<url>''':: the URL of the file upload handler. You may include this explicitly, or use '''<UPLOAD_URL/>''' to use the URL in your project's config.xml file. |
| 85 | '''<open_name>''':: the "logical name" by which your application will reference the file. |
| 86 | '''<optional>''':: if false, your application must create the file, otherwise the job will be marked as an error. |
| 87 | '''<no_validate>''':: if true, don't include this file in the result validation process (relevant only if you are using the sample bitwise validator). |
| 88 | |
| 89 | Other [BoincFiles#Fileproperties output file] and [BoincFiles#Filereferences the way it's referenced]. |
| 90 | |
| 91 | Note: when a job is created, the name of its output template file is stored in the database. |