Changes between Version 18 and Version 19 of GuiRpcProtocol

Timestamp:

Sep 9, 2008, 9:03:32 AM (16 years ago)

Author:

Nicolas

Comment:

--

GuiRpcProtocol

@@ -11 +11 @@
 
 Requests 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 core client 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.
-Ought this to be read as "''must always send the __`<boinc_gui_rpc_reply>`__ root tag''"?
+>> clients must not rely on this, and must always send the __`<boinc_gui_rpc_request>`__ root tag.
+>Ought this to be read as "''must always send the __`<boinc_gui_rpc_reply>`__ root tag''"?
+Nope. I'm talking of RPC clients (which make __requests__), such as BOINCView or the official manager. See second paragraph of this page :)
 
 The current official core client (RPC server) doesn't support pipelining of requests (pipelining means sending a batch of multiple requests without waiting for a reply, then getting all the replies together; this improves latency). For compatibility, pipelining must not be used.