Changes between Version 1 and Version 2 of FileUpload
- Timestamp:
- Apr 25, 2007, 12:17:28 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FileUpload
v1 v2 1 1 = Data server protocol = 2 2 3 Core client communicate with data servers using HTTP. A data server is typically implemented using a web server together with a BOINC-supplied CGI program, '''file_upload_handler'''. 4 === Download === 5 File download is done by a GET request to a URL from the FILE_INFO element. The file offset, if any, is given in '''Range:''' attribute of the HTTP header. 3 Core client communicate with data servers using HTTP. A data server is typically implemented using a web server together with a BOINC-supplied CGI program, '''file_upload_handler'''. 6 4 5 == Download == 7 6 8 === Upload === 9 File upload is done using POST operations to a CGI program. A security mechanism prevents unauthorized upload of large amounts of data to the server. Two RPC operations are used. 7 File download is done by a normal GET request to a URL from the FILE_INFO element. The file offset, if any, is given in '''Range:''' attribute of the HTTP header. 8 9 == Upload == 10 11 File upload is done using POST operations to a CGI program. A security mechanism prevents unauthorized upload of large amounts of data to the server. Two RPC operations are used. 10 12 11 13 '''1) Get file size''' 12 14 13 15 The request message has the form: 14 15 16 16 17 {{{ … … 22 23 </data_server_request> 23 24 }}} 24 The reply message has the form:25 25 26 The reply message has the form: 26 27 27 28 {{{ … … 32 33 </data_server_reply> 33 34 }}} 34 Status is35 35 36 '''''':: 37 Success. Nbytes is 0 if the file doesn't exist. 36 Status is: 37 (empty):: 38 Success. `Nbytes` is 0 if the file doesn't exist. 38 39 '''1''':: 39 40 Transient error. The client should try another data server, or try this one later. 40 41 '''-1''':: 41 Permanent error. 42 In the error cases, the <file_size>element is omitted and the <message> element gives an explanation.42 Permanent error. The client should give up on the result. 43 In the error cases, the `<file_size>` element is omitted and the <message> element gives an explanation. 43 44 44 45 '''2) Upload file''' 45 46 46 47 Request message format: 47 48 48 49 49 {{{ … … 66 66 (no closing tags) 67 67 }}} 68 The <file_info> element is the exact text sent from the scheduling server to the client. It includes a signature based on the project's file upload authentication key pair. <nbytes> is the size of the file. <md5_cksum> is MD5 of the entire file. <offset> is the offset within the file. 68 69 The <file_info> element is the exact text sent from the scheduling server to the client. It includes a signature based on the project's file upload authentication key pair. <nbytes> is the size of the file. <md5_cksum> is MD5 of the entire file. <offset> is the offset within the file. 69 70 70 71 Reply message format: 71 72 72 73 73 {{{ … … 77 77 </data_server_reply> 78 78 }}} 79 Status is80 79 81 '''''':: 80 Status is: 81 82 (empty):: 82 83 success 83 84 '''1'''::
