XML-RPC

XML-RPC is a remote procedure call (RPC) protocol which uses XML to encode its calls and HTTP as a transport mechanism.

Uses your system voice; voice and rate in settings.

Snapshot

≈ 3 min read

Names in other languages

No names in other languages are held for this entry yet.

Article bodies are English and are not machine-translated. A name in another language is not a translation of the article.

XML-RPC is a remote procedure call (RPC) protocol which uses XML to encode its calls and HTTP as a transport mechanism.

History

The XML-RPC protocol was created in 19981 by Dave Winer of UserLand Software and Microsoft, with Microsoft seeing the protocol as an essential part of scaling up its efforts in business-to-business e-commerce. As new functionality was introduced, the standard evolved into what is now SOAP.

UserLand supported XML-RPC from version 5.1 of its Frontier web content management system, released in June 1998. XML-RPC's idea of a human-readable-and-writable, script-parsable standard for HTTP-based requests and responses has also been implemented in competing specifications such as Allaire's Web Distributed Data Exchange (WDDX) and webMethod's Web Interface Definition Language (WIDL).

Prior art wrapping COM, CORBA, and Java RMI objects in XML syntax and transporting them via HTTP also existed in DataChannel's WebBroker technology. The generic use of XML for remote procedure call (RPC) was patented by Phillip Merrick, Stewart Allen, and Joseph Lapp in April 2006, claiming benefit to a provisional application filed in March 1998.

The patent was assigned to webMethods, located in Fairfax, Virginia. The patent expired on March 23, 2019.

Usage

In XML-RPC, a client performs an RPC by sending an HTTP request to a server that implements XML-RPC and receives the HTTP response. A call can have multiple parameters and one result. The protocol defines a few data types for the parameters and result.

Some of these data types are complex, i.e. nested. For example, you can have a parameter that is an array of five integers. 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 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.

JSON-RPC is similar to XML-RPC.

Data types

Common datatypes are converted into their XML equivalents with example values shown below:

Examples

An example of a typical XML-RPC request would be: examples.getStateName 40 An example of a typical XML-RPC response would be: South Dakota A typical XML-RPC fault would be: faultCode 4 faultString Too many parameters.

See also

Weblogs.com Pingback Ajax (programming) Component technologies Comparison of data serialization formats OPML JSON-RPC Web service gRPC

Text derived from https://en.wikipedia.org/w/index.php?oldid=1371162230 under CC BY-SA 4.0; modifications have been made.

References

  1. ↩Wikipedia “XML-RPC” revision 1371162230 · retrieved 2026-10-20 release date (×1) · confidence 0.95 revision URL