Changes between Version 1 and Version 2 of RpcProtocol


Ignore:
Timestamp:
04/25/07 14:17:29 (11 years ago)
Author:
Nicolas
Comment:

Required manual changes to automatic conversion.

Legend:

Unmodified
Added
Removed
Modified
  • RpcProtocol

    v1 v2  
    11= The BOINC scheduling server protocol =
    22
     3== Protocol nucleus ==
    34
    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 
     5The 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:
    76
    87{{{
     
    1413</scheduler_request>
    1514}}}
    16  The 'platform' and version number elements identify the version of the core client originating the request.  The form of the reply is:
    1715
     16The 'platform' and version number elements identify the version of the core client originating the request.
     17
     18The form of the reply is:
    1819
    1920{{{
     
    2526</scheduler_reply>
    2627}}}
    27   Each '''message''' element is a message to the participant.
    2828
     29Each '''message''' element is a message to the participant.
    2930
    3031 * 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.
     
    3738A '''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.
    3839
    39 
    40 === Extensible protocol ===
    41  The remaining protocol may evolve over time. Request elements include
    42 
     40== Extensible protocol ==
     41The remaining protocol may evolve over time. Request elements include
    4342
    4443{{{
     
    109108</result>
    110109}}}
    111   Reply elements include
    112110
     111Reply elements include
    113112
    114113{{{