SUPPORT THE WORK

GetWiki

XML-RPC

ARTICLE SUBJECTS
aesthetics  →
being  →
complexity  →
database  →
enterprise  →
ethics  →
fiction  →
history  →
internet  →
knowledge  →
language  →
licensing  →
linux  →
logic  →
method  →
news  →
perception  →
philosophy  →
policy  →
purpose  →
religion  →
science  →
sociology  →
software  →
truth  →
unix  →
wiki  →
ARTICLE TYPES
essay  →
feed  →
help  →
system  →
wiki  →
ARTICLE ORIGINS
critical  →
discussion  →
forked  →
imported  →
original  →
XML-RPC
[ temporary import ]
please note:
- the content below is remote from Wikipedia
- it has been imported raw for GetWiki
{{Distinguish|text = the use of XML for RPC, independently of the specific protocol. This article is about the protocol named "XML-RPC"}}{{Refimprove|date=October 2016}}{{Use dmy dates|date=October 2012}}XML-RPC is a remote procedure call (RPC) protocol which uses XML to encode its calls and HTTP as a transport mechanism.Simon St. Laurent, Joe Johnston, Edd Dumbill. (June 2001) Programming Web Services with XML-RPC. O'Reilly. First Edition.

History

The XML-RPC protocol was created in 1998 by Dave Winer of UserLand Software and Microsoft,WEB, Box, Don, A Brief History of SOAP, O'Reilly, 1 April 2001,weblink|array|

1404
Something here
1
|base64|eW91IGNhbid0IHJlYWQgdGhpcyE=|Base64-encoded binary data|boolean|1|date/time|19980717T14:08:55|Date and time in ISO 8601 format|double|-12.53|Double precision floating point number|integer|42or42|Whole number, integer|string|Hello world!orHello world!|struct|

foo
1


bar
2
|Associative array|nil|
TITLE=XML'S NEXT STEP ACCESSDATE=2015-11-17 URL=HTTP://WWW.ZDNET.COM/PCMAG/STORIES/TRENDS/0,7607,2286488,00.HTML ARCHIVEURL=HTTPS://WEB.ARCHIVE.ORG/WEB/20000304215507/HTTP://WWW.ZDNET.COM/PCMAG/STORIES/TRENDS/0,7607,2286488,00.HTML SOAP (protocol)>SOAP.WALSH >FIRST=JEFF WORK=INFOWORLD DATE=1999-07-10 DEADURL=YES ARCHIVEDATE=14 SEPTEMBER 1999, UserLand supported XML-RPC from version 5.1 of its Frontier web content management system, released in June 1998.WEB, Walsh, Jeff, UserLand releases Frontier 5.1, drops freeware model, InfoWorld, November 17, 2015, June 29, 1998,weblinkweblink" title="web.archive.org/web/19990915175718weblink">weblink 15 September 1999, 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).NEWS, Udell, Jon, Exploring XML-RPC: DCOM? CORBA? RMI? Why Not Just XML-RPC?, Byte, 2015-11-17, 1999-06-07,weblink yes,weblink" title="web.archive.org/web/20000304171225weblink">weblink 4 March 2000, Prior art wrapping COM, CORBA, and Java RMI objects in XML syntax and transporting them via HTTP also existed in DataChannel's WebBroker technology.NEWS, 20, 21, Walsh, Jeff, W3C gives a nod to DataChannel's WebBroker, Infoworld, 2015-11-17, 1998-05-25,weblink yes,weblink" title="web.archive.org/web/19990910213004weblink">weblink 10 September 1999, WEB, Vizard, Michael, Walsh, Jeff, DataChannel's Dave Pool talks about shaping the role of XML to suit different needs, Infoworld, 2015-12-08, 1998-06-29,weblink yes,weblink" title="web.archive.org/web/19990916093829weblink">weblink 16 September 1999, 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 is assigned to webMethods, located in Fairfax, VA.WEB,weblink US Patent 7,028,312, 18 September 2008, Merrick, 11 April 2006, etal,

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.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 andXML-RPC is that the RESTful protocol uses 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:{| class="wikitable"!Name!Tag Example!Description
Array data structure>Array of values, storing no keys
Boolean datatype>Boolean logical value (0 or 1)
XML#Characters and escaping>XML encoding.
nullable type>Discriminated null value; an XML-RPC weblink" title="web.archive.org/web/20050911054235weblink">extension

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.



Criticism

Recent critics (from 2010 and onwards) of XML-RPC argue that RPC calls can be made with plain XML, and that XML-RPC does not add any value over XML. Both XML-RPC and XML require an application-level data model, such as which field names are defined in the XML schema or the parameter names in XML-RPC. Furthermore, XML-RPC uses about 4 times the number of bytes compared to plain XML to encode the same objects, which is itself verbose compared to JSON.WEB,weblink What is the benefit of XML-RPC over plain XML?, 9 September 2009, Stack Overflow, 7 April 2011, WEB,weblink An open poll on the merits of XmlRpc versus alternatives, 22 November 2006, www.intertwingly.net, 7 April 2011, WEB
,weblink
, If you have REST, why XML-RPC?
, Jon Canady
, 14 January 2010
, joncanady.com
, 7 April 2011
, yes
,weblink" title="web.archive.org/web/20130511053512weblink">weblink
, 11 May 2013
,

See also

References

{{reflist|colwidth=30em}}

External links

  • {{Official| 1=http://www.xmlrpc.com/ }}


- content above as imported from Wikipedia
- "XML-RPC" does not exist on GetWiki (yet)
- time: 2:01am EDT - Tue, Jun 25 2019
[ this remote article is provided by Wikipedia ]
LATEST EDITS [ see all ]
GETWIKI 09 MAY 2016
GETWIKI 18 OCT 2015
M.R.M. Parrott
Biographies
GETWIKI 20 AUG 2014
GETWIKI 19 AUG 2014
GETWIKI 18 AUG 2014
Wikinfo
Culture
CONNECT