<?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"
	>
<channel>
	<title>Comments on: The REST schism and the REST contradiction</title>
	<atom:link href="http://www.megginson.com/blogs/quoderat/2006/03/25/the-rest-schism-and-the-rest-contradiction/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.megginson.com/blogs/quoderat/2006/03/25/the-rest-schism-and-the-rest-contradiction/</link>
	<description>what was</description>
	<pubDate>Fri, 19 Mar 2010 11:16:48 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Jonnay</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/03/25/the-rest-schism-and-the-rest-contradiction/#comment-4652</link>
		<dc:creator>Jonnay</dc:creator>
		<pubDate>Tue, 23 May 2006 00:02:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/03/25/the-rest-schism-and-the-rest-contradiction/#comment-4652</guid>
		<description>I stay out of the REST is better then WS-* argument, because I don't have any firm numbers to state which is better.  I personally prefer REST.

My problem was that defining REST in terms of HTTP verbs is missing the whole point of rest.</description>
		<content:encoded><![CDATA[<p>I stay out of the REST is better then WS-* argument, because I don&#8217;t have any firm numbers to state which is better.  I personally prefer REST.</p>
<p>My problem was that defining REST in terms of HTTP verbs is missing the whole point of rest.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pwb</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/03/25/the-rest-schism-and-the-rest-contradiction/#comment-3013</link>
		<dc:creator>pwb</dc:creator>
		<pubDate>Mon, 27 Mar 2006 19:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/03/25/the-rest-schism-and-the-rest-contradiction/#comment-3013</guid>
		<description>If someone came out with a plain way to describe how to create a "restful API" and gave it a name (a la "Ajax"), people would switch to it in a second. The problem is that REST's current primary documentation is a doctoral dissertation that is mostly unintelligible to a normal human being.

Secondly, REST backers need to come to a conclusion on whether ot not PUT is necessary (no one ever DELETEs).

Finally, once there is some common understanding of (the son of) REST, we should document how some popular APIs would look (e.g., Amazon, Flickr, Bloglines, etc.).</description>
		<content:encoded><![CDATA[<p>If someone came out with a plain way to describe how to create a &#8220;restful API&#8221; and gave it a name (a la &#8220;Ajax&#8221;), people would switch to it in a second. The problem is that REST&#8217;s current primary documentation is a doctoral dissertation that is mostly unintelligible to a normal human being.</p>
<p>Secondly, REST backers need to come to a conclusion on whether ot not PUT is necessary (no one ever DELETEs).</p>
<p>Finally, once there is some common understanding of (the son of) REST, we should document how some popular APIs would look (e.g., Amazon, Flickr, Bloglines, etc.).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Baker</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/03/25/the-rest-schism-and-the-rest-contradiction/#comment-3008</link>
		<dc:creator>Mark Baker</dc:creator>
		<pubDate>Sun, 26 Mar 2006 18:38:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/03/25/the-rest-schism-and-the-rest-contradiction/#comment-3008</guid>
		<description>I think it's important to note that what's demonstrated to work is indeed GET and POST, but *GET and POST as defined*.  I suspect that when Don says "POST" he's implicitly encompassing both tunneled and non-tunneled uses of POST.

Also, GET and POST used as defined is RESTful, and nothing in REST says that you have to use all methods.  It only says you have to use the right one for the job (per self-description).  If you only need to get data, or submit it for processing, then only using GET and POST is just fine.</description>
		<content:encoded><![CDATA[<p>I think it&#8217;s important to note that what&#8217;s demonstrated to work is indeed GET and POST, but *GET and POST as defined*.  I suspect that when Don says &#8220;POST&#8221; he&#8217;s implicitly encompassing both tunneled and non-tunneled uses of POST.</p>
<p>Also, GET and POST used as defined is RESTful, and nothing in REST says that you have to use all methods.  It only says you have to use the right one for the job (per self-description).  If you only need to get data, or submit it for processing, then only using GET and POST is just fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Restiness</title>
		<link>http://www.megginson.com/blogs/quoderat/2006/03/25/the-rest-schism-and-the-rest-contradiction/#comment-2998</link>
		<dc:creator>Restiness</dc:creator>
		<pubDate>Sat, 25 Mar 2006 20:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/archives/2006/03/25/the-rest-schism-and-the-rest-contradiction/#comment-2998</guid>
		<description>[...] David Megginson: &#8220;I do see a contradiction between the two arguments I hear most often from REST supporters 1. REST is superior to Web Services/SOAP/SOA because it’s been proven to work on the Web. 2. Almost nobody on the Web uses REST correctly.&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] David Megginson: &#8220;I do see a contradiction between the two arguments I hear most often from REST supporters 1. REST is superior to Web Services/SOAP/SOA because it’s been proven to work on the Web. 2. Almost nobody on the Web uses REST correctly.&#8221; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
