Changes between Version 6 and Version 7 of GuiRpcProtocol


Ignore:
Timestamp:
May 15, 2008, 5:56:49 PM (16 years ago)
Author:
Nicolas
Comment:

Add info about closing the connection. Split auth, success, error, etc. into a new section "Common replies".

Legend:

Unmodified
Added
Removed
Modified

  • GuiRpcProtocol

    v6 v7  
    1111
    1212Note that the 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.
     13
     14To terminate the RPC session, just close the connection on the client side. Warning: some protocols have a specific "quit" command for this. The GUI RPC protocol has a {{{<quit/>}}} command, but it has a '''completely different purpose: killing the RPC server''' (core client).
     15
     16== Common replies ==
    1317
    1418If a command requires [#auth authentication] but the client hasn't authenticated yet, the RPC server will reply