Changes between Version 1 and Version 2 of RpcProtocol
- Timestamp:
- Apr 25, 2007, 2:17:29 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RpcProtocol
v1 v2 1 1 = The BOINC scheduling server protocol = 2 2 3 == Protocol nucleus == 3 4 4 === Protocol nucleus === 5 The core client communicates with scheduling servers using HTTP. The following 'nucleus' of the protocol should be considered immutable. This will allow any version of the core client to talk to any version of the scheduling server, and for the server, if needed, to tell the core client that it's out of date. The form of the request is: 6 5 The core client communicates with scheduling servers using HTTP. The following 'nucleus' of the protocol should be considered immutable. This will allow any version of the core client to talk to any version of the scheduling server, and for the server, if needed, to tell the core client that it's out of date. The form of the request is: 7 6 8 7 {{{ … … 14 13 </scheduler_request> 15 14 }}} 16 The 'platform' and version number elements identify the version of the core client originating the request. The form of the reply is:17 15 16 The 'platform' and version number elements identify the version of the core client originating the request. 17 18 The form of the reply is: 18 19 19 20 {{{ … … 25 26 </scheduler_reply> 26 27 }}} 27 Each '''message''' element is a message to the participant.28 28 29 Each '''message''' element is a message to the participant. 29 30 30 31 * If the priority is 'high', the core client should try to ensure that the participant sees the message; for example, by displaying it in a popup window. It should not, however, wait for user input, as this could starve other projects. This should be reserved for situations where definitive action is required, e.g. the user must download a new version of the core client in order to continue participating in this project. … … 37 38 A '''redirect''' element gives the URL for a scheduling server for this project. If present, the core client should replace its list of scheduling servers for this project. The reply may contain multiple '''redirect''' elements. 38 39 39 40 === Extensible protocol === 41 The remaining protocol may evolve over time. Request elements include 42 40 == Extensible protocol == 41 The remaining protocol may evolve over time. Request elements include 43 42 44 43 {{{ … … 109 108 </result> 110 109 }}} 111 Reply elements include112 110 111 Reply elements include 113 112 114 113 {{{
