XML-RPC API

PEAR Switches from XML-RPC to REST

Earlier this year, PEAR, the PHP Extension and Application Repository, decided to close down its XML-RPC interface in favor of a REST approach:

As promised, XML-RPC has been disabled at pear.php.net.  Information is now   served via REST files at pear.php.net/rest.  If you are using   a PEAR version earlier than 1.4.0, you will need to manually upgrade PEAR using   direct URLs.  To upgrade to the latest PEAR, you can either use go-pear   (http://pear.php.net/go-pear) or   upgrade using direct URLs ...

REST uses simple HTTP requests to send and receive information. XML-RPC is slightly more complex because it requires remote procedure calls sent over HTTP.

WordPress Adds XML-RPC Weblog Comment API

The first release candidate of WordPress 2.7, released today, includes support for a new XML-RPC API that can be used to submit, edit and delete comments on a WordPress blog.

The WordPress Comments API includes the following methods:

• wp.getComment(blog_id, username, password, comment_id)

• wp.getComments(blog_id, username, password, {status, post_id, number, offset}

• wp.deleteComment(blog_id, username, password, comment_id)

• wp.editComment(blog_id, username, password, comment_id, {status,
  date_created_gmt, content, author, author_url, author_email})

• wp.newComment(blog_id, username, password, post, {content, author,
  author_email, author_url})

• wp.getCommentStatusList(blog_id, username, password)

The documentation is still skimpy at this point, but most of the methods and parameters match those in the MetaWeblog API, an API for reading and writing weblog posts. The parameters enclosed within squiggly brackets ("{ and }") are probably a struct, though until we have a chance to test that theory it's just an educated guess.

The other blog publishing platforms such as TypePad and the other Six Apart software ought to implement this API.

Wanted: XML-RPC Java Programmer

A request has gone out on RentACoder for a Java programmer who can create an XML-RPC client for an unspecified web service:

I am searching for an experienced java coder who can code following:

- Search for a simple service on the internet which is accesible via xml-rpc.
- Code a client which consumes this service

Please find a simple service which returns a String

This appears to be an extremely low-budget project, which is taking bids from prospective coders until Dec. 15.

Choosing Between XML-RPC and REST

Ken Maier, a director of integrated solutions at Verio, asks an interesting question on LinkedIn Answers:

If you had the chance to build an enterprise API from scratch, would you base it on REST or  XML-RPC? Why? Would you pick something else entirely? If so, what?

There's no distinct advantage that makes one approach better than the other in all circumstances. I favor XML-RPC because I've been using Apache XML-RPC for years and can develop XML-RPC clients and servers quickly using the Java class library.

If you have a good HTTP library for reading and writing requests over the web, all you need to employ REST is something to process XML.

Because Maier's working on an enterprise API, I wonder why he isn't also considering SOAP, the extended API that shares a common origin with XML-RPC but is much more heavily weighed towards the demands of the enterprise.

XML-RPC Development News

This site has been established to provide a central place for news and information related to XML-RPC, the web services protocol. Over time we'll add reference documents, notes for programmers, and news announcements pertaining to the technology. Thanks for visiting.