XML-RPC deprecation?
This wouldn’t happen for a long time, but we’re considering deprecating XML-RPC, and here’s why:
- The majority of new applications using the API are using REST rather than XML-RPC.
- REST is far easier to develop for and debug - you just use any web browser.
- REST responses are more human-readable, making it easier to develop
- Maintaining XML-RPC takes a lot more time and energy than REST
- We’d rather spend those resources on things like JSON
But we’re not gonna make any decisions or do anything until we get feedback from our API customers. So please, let us know if XML-RPC development is important to you and why.
November 12th, 2006 at 10:15 am
Why wouldn’t you just publish a WSDL Api that would allow a soap or rest interface?
With a soap interface, one would just create an object in whatever platform they are developing against (soap.py, .net, java, etc) and make a few method calls instead of futzing around with http.
Of course nobody is going to use XML-RPC, it was simply a prototype for soap and was obsolete years ago, and hard to develop against.
November 12th, 2006 at 12:21 pm
@Doug:
Because I hate SOAP. It makes doing simple things very difficult. The whole point of web services APIs like ours is to make them easily accessible and consumable.
REST, JSON, and serialized PHP meet this model. XML-RPC does, too, it’s just less useful. SOAP definitely does not.
November 16th, 2006 at 11:02 pm
[...] smugblog: the APIgetting down and dirty « XML-RPC deprecation? [...]