] as a transport mechanism.
XML-RPC is a very simple protocol, defining only a handful of data types and commands, and the entire description can be printed on two pages of paper. This is in stark contrast to most RPC systems, where the standards documents often run into the hundreds of pages and require considerable software support in order to be used.
XML-RPC was created in 1998 by Dave Winer of UserLand Software and Microsoft. As new functionality was introduced, the standard evolved into what is now SOAP.
XML-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 is assigned to webMethods, located in Fairfax, VA.
Some people prefer XML-RPC to SOAP because of its simplicity, minimalism, and ease of use.
JSON-RPC is similar to XML-RPC.
| Name | Tag Example | Description |
|---|---|---|
| array |
| Array of values, storing no keys |
| base64 |
| Base64-encoded binary data |
| boolean |
| Boolean logical value (0 or 1) |
| date/time |
| Date and time in ISO 8601 format |
| double |
| Double precision floating point number |
| integer |
| Whole number, integer |
| string |
| String of characters. Must follow XML encoding. |
| struct |
| Associative array |
| nil |
| Discriminated null value; an XML-RPC extension |
An example of a typical XML-RPC request would be:
An example of a typical XML-RPC response would be:
A typical XML-RPC fault would be:
: Secure Apache XML-RPC