Submitted by Piotr (not verified) on Tue, 02/23/2010 - 12:38.
I'm just wondering what makes you think XML-RPC technology is outdated? Especially in comparison with RESTful approach utilizing the very basic concepts behind HTTP itself (which can hardly be considered as new being developed in early nineties). Without any solid arguments it's like debating about superiority of Easter over Christmas, or if rounded corners look cool (hint: they don't.)
The other problem is that XML-RPC is a specification, or a well defined protocol while REST is a development style with no details whatsoever. I can't help thinking XML-RPC protocol can be used as a RESTful service. That may sound a bit silly at first, but my point is as long as one can route the requests the proper way these two can be implemented in a very same (or a very similar at least) manner. Let's have a look at XML-RPC protocol as a RESTful service by following RESTful service constrains:
Client-server architecture - XML-RPC client is independent from the server, a different programming language might be and often is used - checked
Stateless - of course checked
Cacheable - it's extremely easy to cache and manage (revalidate, flush) XML data - checked
Layered system - well, checked
Code on demand - never tried it myself but since I like to be right - checked!
Uniform interface - XML as data transfer layer - CHECKED!
To summarise, even if XML-RPC might not be your best choice, it still can be a valid RESTful service if implemented properly.
I'm just wondering what makes
I'm just wondering what makes you think XML-RPC technology is outdated? Especially in comparison with RESTful approach utilizing the very basic concepts behind HTTP itself (which can hardly be considered as new being developed in early nineties). Without any solid arguments it's like debating about superiority of Easter over Christmas, or if rounded corners look cool (hint: they don't.)
The other problem is that XML-RPC is a specification, or a well defined protocol while REST is a development style with no details whatsoever. I can't help thinking XML-RPC protocol can be used as a RESTful service. That may sound a bit silly at first, but my point is as long as one can route the requests the proper way these two can be implemented in a very same (or a very similar at least) manner. Let's have a look at XML-RPC protocol as a RESTful service by following RESTful service constrains:
Client-server architecture - XML-RPC client is independent from the server, a different programming language might be and often is used - checked
Stateless - of course checked
Cacheable - it's extremely easy to cache and manage (revalidate, flush) XML data - checked
Layered system - well, checked
Code on demand - never tried it myself but since I like to be right - checked!
Uniform interface - XML as data transfer layer - CHECKED!
To summarise, even if XML-RPC might not be your best choice, it still can be a valid RESTful service if implemented properly.