XML-RPC

XML-RPC is a remote procedure call protocol which uses XML to encode its calls and HTTP as a transport mechanism. It 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 thousands of pages and require considerable software support in order to be used.

It was first created by Dave Winer of UserLand Software in 1998 with Microsoft. As new functionality was introduced, the standard evolved into what is now SOAP.

Data types

1404 Something here 1 foo 1 bar 2

Name	Tag Example	Description
array		Array of values, storing no keys
base64	eW91IGNhbid0IHJlYWQgdGhpcyE=	Base 64-encoded binary data
boolean	1	Boolean logical value (0 or 1)
date/time	19980717T14:08:55	Date and time
double	-12.53	Double precision floating number
integer	42 or 42	Whole number, integer
string	Hello world!	String of characters. Must follow XML encoding.
struct		Array of values, storing keys
nil		Discriminated null value; an XML-RPC extension

Examples

An example of a typical XML-RPC request would be: examples.getStateName 41

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.

External links

XML-RPC Homepage
Forum
Tutorials
Technology Reports
Citations from CiteSeer
Jabber-RPC is XML-RPC over the Jabber protocol.
Secure Apache XML-RPC
RemObjects SDK provides support for XML-RPC, in addition to SOAP and others.

XML-based standards | Web services | Inter-process communication

Gourt Home::Gourt :: XML-RPC

Data types

Examples

See also

External links