XML-RPC: Difference between revisions

Revision as of 19:03, 11 May 2020

Revision as of 14:01, 17 June 2020

Line 27:

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

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

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