<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: A bit on RESTful webservices</title>
	<atom:link href="http://www.conradstrydom.com/2009/02/10/a-bit-on-restful-webservices/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.conradstrydom.com/2009/02/10/a-bit-on-restful-webservices/</link>
	<description>views and commentary from a web engineer</description>
	<lastBuildDate>Tue, 31 Mar 2009 09:33:36 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stii</title>
		<link>http://www.conradstrydom.com/2009/02/10/a-bit-on-restful-webservices/comment-page-1/#comment-35</link>
		<dc:creator>Stii</dc:creator>
		<pubDate>Thu, 19 Feb 2009 17:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://conradstrydom.wordpress.com/?p=116#comment-35</guid>
		<description>No, I hear you! REST is not a silver bullet. There are some instances (like your example) where it is not 100% practical.</description>
		<content:encoded><![CDATA[<p>No, I hear you! REST is not a silver bullet. There are some instances (like your example) where it is not 100% practical.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dewald Botha</title>
		<link>http://www.conradstrydom.com/2009/02/10/a-bit-on-restful-webservices/comment-page-1/#comment-34</link>
		<dc:creator>Dewald Botha</dc:creator>
		<pubDate>Thu, 19 Feb 2009 17:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://conradstrydom.wordpress.com/?p=116#comment-34</guid>
		<description>@Stii:  Yip - i agree, but the problem I always found with REST is when you try to go too deep into the rabbit hole.

Take for example a call where one would like to pull all users from a site with a user ID between 1 and 10, who has joined between 2008 and 2009 with the surname &#039;DOE&#039;.

You could translate that into a REST URI, but it would end up probably being longer than the wall of China.

I think one has too find a balance between using a stateless interface such as REST and something such as XML-RPC or SOAP.

Maybe a RESTful SOAP service - ROAP. :-)</description>
		<content:encoded><![CDATA[<p>@Stii:  Yip &#8211; i agree, but the problem I always found with REST is when you try to go too deep into the rabbit hole.</p>
<p>Take for example a call where one would like to pull all users from a site with a user ID between 1 and 10, who has joined between 2008 and 2009 with the surname &#8216;DOE&#8217;.</p>
<p>You could translate that into a REST URI, but it would end up probably being longer than the wall of China.</p>
<p>I think one has too find a balance between using a stateless interface such as REST and something such as XML-RPC or SOAP.</p>
<p>Maybe a RESTful SOAP service &#8211; ROAP. <img src='http://www.conradstrydom.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stii</title>
		<link>http://www.conradstrydom.com/2009/02/10/a-bit-on-restful-webservices/comment-page-1/#comment-33</link>
		<dc:creator>Stii</dc:creator>
		<pubDate>Mon, 16 Feb 2009 11:09:43 +0000</pubDate>
		<guid isPermaLink="false">http://conradstrydom.wordpress.com/?p=116#comment-33</guid>
		<description>Dewald, I think there is a quest for API and site to become one. I.o.w. if you have RPC web services you always have to maintain it separately to your site. REST allows you to sort of close that gap in that both human and machine can use the same thing.</description>
		<content:encoded><![CDATA[<p>Dewald, I think there is a quest for API and site to become one. I.o.w. if you have RPC web services you always have to maintain it separately to your site. REST allows you to sort of close that gap in that both human and machine can use the same thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Conrad</title>
		<link>http://www.conradstrydom.com/2009/02/10/a-bit-on-restful-webservices/comment-page-1/#comment-32</link>
		<dc:creator>Conrad</dc:creator>
		<pubDate>Wed, 11 Feb 2009 11:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://conradstrydom.wordpress.com/?p=116#comment-32</guid>
		<description>IMHO the biggest difference between REST and RPC is that REST is noun based (don&#039;t confuse with the HTTP verbs) and RPC is verb based.

Example of REST noun interaction:
/user/1

vs RPC verb interaction
getUser: 1

The main difference here is that the REST implementation has a single unified interface to your objects (nouns) and is easy to use for developers when adding new objects etc.

The appropriate verbs to use with RPC is not that obvious from the word go and the net effect of a particular action is not that clear either and may become ambigious. Anyhow .. just my 2 cents.</description>
		<content:encoded><![CDATA[<p>IMHO the biggest difference between REST and RPC is that REST is noun based (don&#8217;t confuse with the HTTP verbs) and RPC is verb based.</p>
<p>Example of REST noun interaction:<br />
/user/1</p>
<p>vs RPC verb interaction<br />
getUser: 1</p>
<p>The main difference here is that the REST implementation has a single unified interface to your objects (nouns) and is easy to use for developers when adding new objects etc.</p>
<p>The appropriate verbs to use with RPC is not that obvious from the word go and the net effect of a particular action is not that clear either and may become ambigious. Anyhow .. just my 2 cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dewald Botha</title>
		<link>http://www.conradstrydom.com/2009/02/10/a-bit-on-restful-webservices/comment-page-1/#comment-31</link>
		<dc:creator>Dewald Botha</dc:creator>
		<pubDate>Wed, 11 Feb 2009 10:01:46 +0000</pubDate>
		<guid isPermaLink="false">http://conradstrydom.wordpress.com/?p=116#comment-31</guid>
		<description>In theory rest seems like an easy solution, but if you are like me you&#039;d prefer the soap/xml-rpc way of doing things.

Okay, I know it is easy to just simply PUT something to an human readable URI, but what&#039;s wrong with calling a function with xml-rpc/soap.

Doesn&#039;t it kind of keep the flavor going with the idea of using objects and functions.

Well, thats just me.</description>
		<content:encoded><![CDATA[<p>In theory rest seems like an easy solution, but if you are like me you&#8217;d prefer the soap/xml-rpc way of doing things.</p>
<p>Okay, I know it is easy to just simply PUT something to an human readable URI, but what&#8217;s wrong with calling a function with xml-rpc/soap.</p>
<p>Doesn&#8217;t it kind of keep the flavor going with the idea of using objects and functions.</p>
<p>Well, thats just me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
