Changes between Version 11 and Version 12 of GuiRpcProtocol


Ignore:
Timestamp:
May 16, 2008, 10:16:06 AM (17 years ago)
Author:
Nicolas
Comment:

Change order of sections

Legend:

Unmodified
Added
Removed
Modified

  • GuiRpcProtocol

    v11 v12  
    4343A notable error message is "unrecognized op", which is returned if the server doesn't recognize a command. The client must be prepared to receive this even in reply to commands documented here, because older core client versions may not support all of them. In fact, it's more reliable to just send a command and fallback to an alternative if "unrecognized op" is returned, than to look at the version number to know what is supported.
    4444
     45== Common XML elements ==
     46There are some XML elements (like {{{<project>}}}, {{{<result>}}}, {{{<workunit>}}}, and {{{<app>}}}) that are common to many command replies. Such elements are documented in this section.
     47
     48The XML responses are relatively flat, and are parsed in one pass. The relationship between XML elements is determined by what was parsed before it, instead of based on the tree hierarchy like other XML formats do. For example, {{{<result>}}} elements that come ''after'' a particular {{{<project>}}} element are results that belong to that project; instead of those results being ''inside'' the {{{<project>}}} element.
     49
    4550== Authentication == #auth
    4651
    … …  
    7580
    7681If the client hasn't authenticated yet, and it is connecting remotely (ie. not via localhost), {{{<auth1/>}}} is the only command that can be sent, and all the rest will return <unauthorized/>.
    77 
    78 == Common XML elements ==
    79 There are some XML elements (like {{{<project>}}}, {{{<result>}}}, {{{<workunit>}}}, and {{{<app>}}}) that are common to many command replies. Such elements are documented in this section.
    80 
    81 The XML responses are relatively flat, and are parsed in one pass. The relationship between XML elements is determined by what was parsed before it, instead of based on the tree hierarchy like other XML formats do. For example, {{{<result>}}} elements that come ''after'' a particular {{{<project>}}} element are results that belong to that project; instead of those results being ''inside'' the {{{<project>}}} element.