Changes between Version 3 and Version 4 of GuiRpc

Timestamp:

Jun 30, 2007, 11:30:48 AM (17 years ago)

Author:

Nicolas

Comment:

--

GuiRpc

@@ -3 +3 @@
 The BOINC core client provides a set of RPCs (remote procedure calls) for control and state interrogation. This enables the development of GUI (graphical user interface) programs separately from the core client. These RPCs send XML request and reply messages over a TCP connection. The XML formats are not documented, but can be deduced from the source code.
 
-BOINC provides a C++ interface to these RPCs, consisting of the GUI_RPC class. The interface is in [source:trunk/boinc/lib/gui_rpc_client.h lib/gui_rpc_client.h], and the program [source:trunk/boinc/lib/boinc_cmd.C boinc_cmd.C] gives a usage example). All member functions return an integer error code.
-It should be easy fairly easy to generate client interfaces in languages other than C++. GUI programs connect to the core client by opening a TCP socket at port 31416. They can then do repeated RPCs over this connection. Each reply message ends with the character '\003. 
+BOINC provides a C++ interface to these RPCs, consisting of the GUI_RPC class. The interface is in [source:trunk/boinc/lib/gui_rpc_client.h lib/gui_rpc_client.h], and the program [source:trunk/boinc/lib/boinc_cmd.C boinc_cmd.C] gives a usage example. All member functions return an integer error code.
+It should be easy fairly easy to generate client interfaces in languages other than C++. GUI programs connect to the core client by opening a TCP socket at port 31416. They can then do repeated RPCs over this connection. Each reply message ends with the character \003.
 
 To create an RPC connection, call
@@ -11 +11 @@
 }}}
 Establish RPC connection to the given host
+
+{{{
+#!comment
+It would be useful if we could link to individual RPCs. I'm not sure if that would need =headers= or there is another way to make anchors.
+}}}
 
 == Dealing with versions ==