Changes between Version 20 and Version 21 of GuiRpcProtocol

Timestamp:

Sep 9, 2008, 9:29:16 AM (16 years ago)

Author:

Pepo

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 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.
->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 :)
+>>> 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 :)
+Thanks for clarification (I've missed the trailing ''s'' in client''s'' and thought of BCC), so you can clean my mess up :-) Maybe write at least once "''...however, RPC clients must not rely on this...''"? Although, with your next change from ''core client'' to ''RPC server'' it should not be necessary anymore.
+
 
 The current 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.