Changes between Version 30 and Version 31 of RemoteJobs
- Timestamp:
- Feb 15, 2013, 1:02:00 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RemoteJobs
v30 v31 1 1 [[PageOutline]] 2 = APIfor remote job submission =2 = Web RPCs for remote job submission = 3 3 4 4 This document describes an API for remotely submitting jobs to a BOINC server. … … 10 10 * There can be no dependencies between jobs. 11 11 12 BOINC provides a PHP library that implements the API.13 The underlying web services are implemented as HTTP/XML RPCs, 14 and it is possible to create bindings in other languages.12 The interface is implemented using XML over HTTP. 13 BOINC provides a client-side PHP binding; 14 it's possible to create bindings in other languages. 15 15 16 16 == Input and output files == 17 17 18 18 Input files can be supplied in any of the following ways: 19 * '''local''': the file is resident on the BOINC server, and is specified by its path.20 19 * '''inline''': the file is included in the job submission request XML message. 21 20 It will be served to clients from BOINC server. 22 * '''semilocal''': the file is on a data server other than the BOINC server. 23 It is specified by its URL. 21 * '''sandbox''': the file is in the user's [RemoteInputFiles#Per-userfilesandbox sandbox], 22 and is specified by its name in the sandbox. 23 * '''local''': the file has been staged on the BOINC server, and is specified by its physical filename. 24 * '''semilocal''': the file is on a data server other than the BOINC server; 25 this data server need not be accessible to the outside world. 26 The file is specified by its URL. 24 27 It will be downloaded by the BOINC server during job submission, 25 28 and served to clients from the BOINC server. … … 30 33 As jobs are completed, their output files are available to the submitting user via HTTP. 31 34 When a batch is complete, a zipped archive of all its output files is available via HTTP. 35 Details are [RemoteOutputFiles here]. 32 36 33 37 == PHP interface ==