xml-rpc协议（XML-RPC protocol）.docVIP

xml-rpc协议（XML-RPC protocol） XML-RPC is a set of specifications and a series of implementations that allow programs running on different operating systems and environments to conduct remote procedure calls based on internet. This remote procedure call uses HTTP as the transport protocol, and XML as the encoding format for the transmission of information. The definition of Xml-Rpc is as simple as possible, but it can transfer, process and return complex data structures at the same time. Xml-rpc is a remote procedure call protocol working on internet. A XML-RPC message is a http-post request for the XML of the request, the invoked method executes on the server side, and the execution result is encoded back in XML format. Procedure call arguments can be scalars, values, strings, dates, etc., or a complex record or list structure (list, structures, that is, array type) Examples of XML-RPC requests: POST /RPC2 HTTP/1.0 User-Agent: Frontier/5.1.2 (WinNT) Host: Content-Type: text/xml Content-length: 181 XML version= 1 methodCall methodNameexamples.getStateName/methodName params param valuei441/i4/value /param /params /methodCall Request header request: In the first line, the format of URI can not be specified. For example, if only it can handle XML-RPC calls, is empty, or just a slash. However, if the server to handle HTTP requests, we should let URI can help routing requests to the XML-RPC request code. (in example, URI is /RPC2, which tells the server to route the request to the RPC2 responder.) User-Agent and Host must be specified Content-Type must be text/xml. Content-Length must be specified and must be correct Payload format: Valid information is in a single XML structure called methodCall The methodCall must contain an methodName subkey, which is a string containing the name of the method (procedure) to call. The string can contain only letters (case A-Z), numbers (0-9), underscores, dots, colons, and slashes (/). The server determines how to interpret the chara