1 Apr 2005 01:48
Re: What Does SOAP/WS Do that A REST System Can't?
Michael Champion <michaelc.champion <at> gmail.com>
2005-03-31 23:48:14 GMT
2005-03-31 23:48:14 GMT
On Wed, 30 Mar 2005 22:00:10 -0500, Michael Champion wrote > I maintain that there is no deep architectural principle here -- > either approach exposes essentially the same order of complexity from > the service provider to the service consumer. As is often the case, David Megginson http://www.megginson.com/blogs/quoderat/archives/2005/03/31/rest-and-rss/ makes a similar point far more eloquently : "REST offloads complexity from the protocol (HTTP) to the content (XML). That makes REST look simple as long as you focus only on the protocol, but RESTafarians cannot get away forever with leaving the content format for data unspecified." His larger point that RSS is to the RESTful data web what HTML is to the document web is very interesting too. That would explain Dare's recent conversion to RESTifarianism(Continue reading)-- in the world of Web-based information services a la MSN, Google, Flickr, Bloglines etc., HTTP+RSS probably does hit the 80/20 point or better. ----------------------------------------------------------------- The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org> The list archives are at http://lists.xml.org/archives/xml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://www.oasis-open.org/mlmanage/index.php>
-- in the world of Web-based
information services a la MSN, Google, Flickr, Bloglines etc.,
HTTP+RSS probably does hit the 80/20 point or better.
-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <
RSS Feed