XML-RPC: Difference between revisions

Revision as of 10:13, 19 December 2017

Revision as of 00:05, 4 May 2018

Line 21:

==Usage==

In XML-RPC, worksa client performs an RPC by sending an HTTP request to a server implementingthat theimplements protocol.XML-RPC Theand clientreceiving inthe thatHTTP caseresponse. is typically software wanting toA call acan singlehave methodmultiple ofparameters aand remoteone systemresult. Multiple inputThe parametersprotocol candefines bea passedfew todata thetypes remotefor method,the oneparameters returnand value is returnedresult. The parameter types allow nestingSome of parametersthese intodata mapstypes andare listscomplex, thusi.e. largernested. structures can be transported.For Thereforeexample, XML-RPCyou can behave useda toparameter transportthat objectsis oran structuresarray bothof asfive input and as output parametersintegers.

The parameters/result structure and the set of data types are meant to mirror those used in common programming languages.

''Identification'' of clients for authorization purposes can be achieved using popular HTTP security methods. [[Basic access authentication]] is used for identification, [[HTTPS]] is used when identification (via certificates) and encrypted messages are needed. Both methods can be combined.

''Identification'' of clients for authorization purposes can be achieved using popular HTTP security methods. [[Basic access authentication]] iscan be used for identification, [[HTTPS]] is used when identification (via certificates) and encrypted messages are needed. Both methods can be combinedauthentication.

In comparison to [[REST]], where ''resource representations'' (documents) are transferred, XML-RPC is designed to ''call methods''.

The protocol does not allow [[HTTPS]], but it is a common and obvious variation to use HTTPS in place of HTTP.

In comparison to [[REST]]ful protocols, where ''resource representations'' (documents) are transferred, XML-RPC is designed to ''call methods''. The practical difference is just that XML-RPC is much more structured, which means common library code can be used to implement clients and servers and there is less design and documentation work for a specific application protocol. One salient technical difference between typical RESTful protocols and

XML-RPC is that the RESTful protocol uses the HTTP URI for parameter information whereas with XML-RPC, the URI just identifies the server.

[[JSON-RPC]] is similar to XML-RPC.