Changes between Version 2 and Version 3 of GuiRpc

Timestamp:

Jun 28, 2007, 5:08:25 PM (17 years ago)

Author:

Nicolas

Comment:

Formatting fix, a few typos fixed, added links to sourcecode

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 lib/gui_rpc_client.h, and the program boinc_cmd.C gives a usage example). All member functions return an integer error 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. 
 
@@ -10 +10 @@
 init(char* host)
 }}}
-        Establish RPC connection to the given host
+Establish RPC connection to the given host
 
 == Dealing with versions ==
@@ -17 +17 @@
 
     * Create a GUI_RPC object and connect. Call exchange_versions() to get the client version.
-    * If exchange_versions() fails (it's not suppored in pre-5.6 clients) do a get_state() RPC, and get the client version from CC_STATE::version_info.
+    * If exchange_versions() fails (it's not supported in pre-5.6 clients) do a get_state() RPC, and get the client version from CC_STATE::version_info.
     * Use the client version number to decide what subsequent RPCs to make (version info is included in the RPC list below). 
 
@@ -253 +253 @@
 }}}
 
-Write the given contents to the global preferences override file. If the argment is an empty string, delete the file. Otherwise the argument must be a valid <global_preferences> element.
+Write the given contents to the global preferences override file. If the argument is an empty string, delete the file. Otherwise the argument must be a valid <global_preferences> element.
 
 {{{