XML-RPC: Difference between revisions

Revision as of 05:18, 15 December 2021

Revision as of 17:41, 29 March 2022

Line 28:

''Identification'' of clients for authorization purposes can be achieved using popular HTTP security methods. [[Basic access authentication]] can be used for identification and authentication.

In comparison to RESTful 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 many RESTful protocols use the HTTP URI for parameter information, whereas with XML-RPC, the URI just identifies the server.

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.