• The job of the server is to process the XML-RPC request for the execution of some piece of code and return a value to the client.
• According to the rules of XML-RPC, a server must return either the result of the procedure execution or a fault element.
• Figure also illustrates the return value of an XML-RPC packaged in the data area of an HTTP reply. Again, as far as HTTP is concerned, it's just data.
• XML-RPC specifies that the response to a procedure call must be a single XML structure, a methodResponse, which can contain either the return value packaged in a single params element or a fault element which contains information about why the fault occurred.
• Figure also illustrates returning a fault element as the payload of an HTTP response.
• As we'll see with SOAP, the specification for describing failure is an important aspect of XML-based protocols.
• According to the rules of XML-RPC, a server must return either the result of the procedure execution or a fault element.
• Figure also illustrates the return value of an XML-RPC packaged in the data area of an HTTP reply. Again, as far as HTTP is concerned, it's just data.
• XML-RPC specifies that the response to a procedure call must be a single XML structure, a methodResponse, which can contain either the return value packaged in a single params element or a fault element which contains information about why the fault occurred.
• Figure also illustrates returning a fault element as the payload of an HTTP response.
• As we'll see with SOAP, the specification for describing failure is an important aspect of XML-based protocols.
No comments:
Post a Comment