FACTOID # 104: ‘Dollar’ is the most common currency name, followed by ‘franc,’ ‘pound,’ ‘dinar,’ ‘peso,’ and ‘rupee.’
 
 Home   Encyclopedia   Statistics   Countries A-Z   Flags   Maps   Education   Forum   FAQ   About 
 
WHAT'S NEW
RELATED ARTICLES
People who viewed "XML RPC" also viewed:
RECENT ARTICLES
More Recent Articles »
 

Encyclopedia > XML RPC

XML-RPC is a remote procedure call protocol encoded in XML. 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 1995 with Microsoft. However Microsoft considered it too simple, and started adding functionality. After several rounds of this, the standard was no longer so simple, and became what is now SOAP.

Contents

Data Types

Name Tag Example Description
array
 <array> <data> <value><i4>1404</i4></value> <value><string>Something Here</string></value> <value><i4>1</i4></value> </data> </array> 
Array of values, storing no keys
base64 <base64>eW91IGNhbid0IHJlYWQgdGhpcyE=</base64> Base 64-encoded binary data
boolean <boolean>1</boolean> Boolean logical value (0 or 1)
date/time <dateTime.iso8601>19980717T14:08:55</dateTime.iso8601> Date and time
double <double>-12.53</double> Double precision floating number
integer <i4>42</i4> Whole number, integer
string <string>Hello world!</string> String of characters. Must follow XML encoding.
struct
 <struct> <member> <name>foo</name> <value><i4>1</i4></value> </member> <member> <name>bar</name> <value><i4>2</i4></value> </member> </struct> 
Array of values, storing keys

Examples

An example of a typical XML-RPC request would be:

 <?xml version="1.0"?> <methodCall> <methodName>examples.getStateName</methodName> <params> <param> <value><i4>41</i4></value> </param> </params> </methodCall> 

An example of a typical XML-RPC response would be:

 <?xml version="1.0"?> <methodResponse> <params> <param> <value><string>South Dakota</string></value> </param> </params> </methodResponse> 

A typical XML-RPC fault would be:

 <?xml version="1.0"?> <methodResponse> <fault> <value> <struct> <member> <name>faultCode</name> <value><int>4</int></value> </member> <member> <name>faultString</name> <value><string>Too many parameters.</string></value> </member> </struct> </value> </fault> </methodResponse> 

See also

web service, component technologies


External links

  • XML-RPC Homepage (http://www.xml-rpc.com/)
  • Forum (http://groups.yahoo.com/group/xml-rpc/)
  • Tutorials (http://www.xml.com/pub/rg/XML_RPC_Tutorials)
  • Technology Reports (http://xml.coverpages.org/xml-rpc.html)
  • Citations from CiteSeer (http://citeseer.org/cs?q=XML+and+RPC)
  • Implementations for ...
    • C and C++ (http://xmlrpc-c.sourceforge.net/)
    • C++ (http://xmlrpcpp.sourceforge.net/)
    • Java (http://xmlrpc.sourceforge.net/)
    • PHP (http://phpxmlrpc.sourceforge.net/)
    • ASP (http://aspxmlrpc.sourceforge.net/)
    • TCL (http://tclsoap.sourceforge.net/XMLRPCDomain.html)
    • Delphi (http://delphixml-rpc.sourceforge.net/)
    • Ruby (http://www.ntecs.de/projects/xmlrpc4r/)
    • Python (http://www.python.org/doc/current/lib/module-xmlrpclib.html)
    • Perl (http://search.cpan.org/~rjray/RPC-XML-0.53/)
    • Flash (http://xmlrpcflash.sourceforge.net/)
    • .NET (http://xml-rpc.net/), C# .NET (http://freshmeat.net/projects/xmlrpccs/)
    • Objective-C/Cocoa (http://www.divisiblebyzero.com/)

 

COMMENTARY     


Share your thoughts, questions and commentary here
Your name
Your location
Your comments
Please enter the 5-letter protection code


Lesson Plans | Student Area | Student FAQ | Reviews | Press Releases |  Feeds | Contact
The Wikipedia article included on this page is licensed under the GFDL.
Images may be subject to relevant owners' copyright.
All other elements are (c) copyright NationMaster.com 2003-5. All Rights Reserved.
Usage implies agreement with terms.