| | 50 | === Remote input files === |
| | 51 | By default, input files are staged locally on the project server, |
| | 52 | and are identified by their filename. |
| | 53 | |
| | 54 | However, you can also use input files that are remote, |
| | 55 | i.e. on a web server other than the project server. |
| | 56 | In that case you must specify them as |
| | 57 | {{{ |
| | 58 | --remote_file filename URL nbytes MD5 |
| | 59 | }}} |
| | 60 | |
| | 81 | |
| | 82 | If you want to use remote input files, use the following variant: |
| | 83 | {{{ |
| | 84 | int create_work( |
| | 85 | DB_WORKUNIT& wu, |
| | 86 | const char* wu_template, // contents, not path |
| | 87 | const char* result_template_filename, // relative to project root |
| | 88 | const char* result_template_filepath, // absolute or relative to current dir |
| | 89 | vector<INFILE_DESC> infiles, // list of input file descriptions; see below |
| | 90 | SCHED_CONFIG&, |
| | 91 | const char* command_line = NULL, |
| | 92 | const char* additional_xml = NULL |
| | 93 | ); |
| | 94 | |
| | 95 | struct INFILE_DESC { |
| | 96 | char name[1024]; // physical name |
| | 97 | bool is_remote; |
| | 98 | // the following defined if remote |
| | 99 | double nbytes; |
| | 100 | char md5[64]; |
| | 101 | char url[1024]; |
| | 102 | }; |
| | 103 | |
| | 104 | }}} |