Changes between Version 23 and Version 24 of GuiRpcProtocol


Ignore:
Timestamp:
Sep 11, 2008, 6:12:34 PM (16 years ago)
Author:
Nicolas
Comment:

Add warning about yet another XML parser brokenness.

Legend:

Unmodified
Added
Removed
Modified

  • GuiRpcProtocol

    v23 v24  
    99
    1010The protocol is based on XML, and it's strictly request-reply. The client sends requests to the server, and waits for a reply; the server never sends anything without getting a request from the client first. Both requests and replies are terminated with the control character `0x03`.
     11
     12Self-closing tags must not have a space before the slash, or current client and server will not parse it correctly. For example, send {{{<authorized/>}}}, not {{{<authorized />}}}.
    1113
    1214Requests are inside `<boinc_gui_rpc_request>` elements, and replies from the RPC server are inside `<boinc_gui_rpc_reply>` elements (in both cases there is a `0x03` byte after the closing tag). The current RPC server implementation doesn't require the `<boinc_gui_rpc_request>` tag, which is handy for debugging (you can connect via [http://netcat.sourceforge.net/ netcat] and just type `<auth1/>`); however, clients must not rely on this, and must always send the `<boinc_gui_rpc_request>` root tag.