We are moving to a model where the GUI (graphical user interface) and the core client are separate programs, communicating using RPC over local pipes. This will make it easy for people to develop new GUIs, and will eliminate security issues related to having GUI code in the core client.
GUI programs connect to the core client by opening a Unix-domain socket named gui_rpc in the core client directory. They can then do repeated RPCs over this connection.
Currently only one RPC is defined. The request message is
", htmlspecialchars("
and the reply message is an XML document describing
the state of the core client.
This has the same format as the client_state.xml file.
Eventually we will add RPCs allowing the GUI to control the core client (e.g. to suspend and resume it, to attach or detach projects, etc.
The BOINC source code distribution includes files
gui_rpc_client.C and gui_rpc_client.h
in the client directory.
These define a class GUI_RPC
that manages the establishment of the RPC pipe,
and that parses the returned XML into a data structure
from which the GUI can be generated.
The project gui_test.C shows how to user this mechanism.
";
page_tail();
?>