<?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: REST: the quick pitch</title>
	<atom:link href="http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/</link>
	<description>XML and the Web.</description>
	<pubDate>Mon, 08 Sep 2008 16:15:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: sideline.ca &#187; Elevator pitch for REST</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-25732</link>
		<dc:creator>sideline.ca &#187; Elevator pitch for REST</dc:creator>
		<pubDate>Tue, 10 Apr 2007 03:18:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-25732</guid>
		<description>[...] &#8220;REST: the quick pitch&#8221; is another good article to read if you&#8217;re trying to wrap your head around REST. It comes complete with an elevator pitch:  With REST, every piece of information has its own URL. [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;REST: the quick pitch&#8221; is another good article to read if you&#8217;re trying to wrap your head around REST. It comes complete with an elevator pitch:  With REST, every piece of information has its own URL. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New JSR to define a high-level REST API for Java &#171; Noelios Consulting</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-25409</link>
		<dc:creator>New JSR to define a high-level REST API for Java &#171; Noelios Consulting</dc:creator>
		<pubDate>Tue, 03 Apr 2007 13:21:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-25409</guid>
		<description>[...] David Megginson (SAX, XML) [...]</description>
		<content:encoded><![CDATA[<p>[...] David Megginson (SAX, XML) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Davis</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-24181</link>
		<dc:creator>Jim Davis</dc:creator>
		<pubDate>Wed, 14 Mar 2007 01:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-24181</guid>
		<description>I agree with "Avoid scripting-language file extensions" but not the first reason you give for it.  Attempting to conceal your framework is illusory protection at best, it's "security through obscurity".  Your second reason is sufficient: it's just encapsulation.  Choice of scripting language or framework is an implementation detail that should not be reflected in the URL.</description>
		<content:encoded><![CDATA[<p>I agree with &#8220;Avoid scripting-language file extensions&#8221; but not the first reason you give for it.  Attempting to conceal your framework is illusory protection at best, it&#8217;s &#8220;security through obscurity&#8221;.  Your second reason is sufficient: it&#8217;s just encapsulation.  Choice of scripting language or framework is an implementation detail that should not be reflected in the URL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bugfox blog &#187; Blog Archive &#187; David Megginson on REST</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-24123</link>
		<dc:creator>bugfox blog &#187; Blog Archive &#187; David Megginson on REST</dc:creator>
		<pubDate>Mon, 12 Mar 2007 18:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-24123</guid>
		<description>[...] David Megginson offers a funny but insightful summary of the most important ideas in REST: The Quick Pitch: [...]</description>
		<content:encoded><![CDATA[<p>[...] David Megginson offers a funny but insightful summary of the most important ideas in REST: The Quick Pitch: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete Lacey's Weblog</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23663</link>
		<dc:creator>Pete Lacey's Weblog</dc:creator>
		<pubDate>Mon, 05 Mar 2007 18:35:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23663</guid>
		<description>&lt;strong&gt;Are you getting sound advice?&lt;/strong&gt;

If you&#8217;re trying to get your arms around this whole REST thing, then the RESTian posts of the last few weeks have made that job a whole lot easier.
David Meggison starts things off with REST: the quick pitch.  Including this wonderful elevator pi...</description>
		<content:encoded><![CDATA[<p><strong>Are you getting sound advice?</strong></p>
<p>If you&#8217;re trying to get your arms around this whole REST thing, then the RESTian posts of the last few weeks have made that job a whole lot easier.<br />
David Meggison starts things off with REST: the quick pitch.  Including this wonderful elevator pi&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pwb</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23555</link>
		<dc:creator>pwb</dc:creator>
		<pubDate>Sat, 03 Mar 2007 05:34:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23555</guid>
		<description>I'm not totally sold on getting rid of querystrings. Querystrings have some advantages including being accessed from s and offering a bit of implicit description.

Which is better?

http://shoes.com/shoes/air-jordan/white/large
http://shoes.com/shoes?style=air-jordan&#38;color=white&#38;size=large</description>
		<content:encoded><![CDATA[<p>I&#8217;m not totally sold on getting rid of querystrings. Querystrings have some advantages including being accessed from s and offering a bit of implicit description.</p>
<p>Which is better?</p>
<p><a href="http://shoes.com/shoes/air-jordan/white/large" rel="nofollow">http://shoes.com/shoes/air-jordan/white/large</a><br />
<a href="http://shoes.com/shoes?style=air-jordan&amp;color=white&amp;size=large" rel="nofollow">http://shoes.com/shoes?style=air-jordan&amp;color=white&amp;size=large</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pwb</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23552</link>
		<dc:creator>pwb</dc:creator>
		<pubDate>Sat, 03 Mar 2007 00:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23552</guid>
		<description>I'mnot totally sold on getting rid of querystrings. They have some advantages. A major one is being accessible via s. Another is that they provide a bit of self description.

Which is better?

http://www.books.com/books/isbn/10231234234
http://www.books.com/books?isbn=10231234234</description>
		<content:encoded><![CDATA[<p>I&#8217;mnot totally sold on getting rid of querystrings. They have some advantages. A major one is being accessible via s. Another is that they provide a bit of self description.</p>
<p>Which is better?</p>
<p><a href="http://www.books.com/books/isbn/10231234234" rel="nofollow">http://www.books.com/books/isbn/10231234234</a><br />
<a href="http://www.books.com/books?isbn=10231234234" rel="nofollow">http://www.books.com/books?isbn=10231234234</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Nilsson</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23497</link>
		<dc:creator>John Nilsson</dc:creator>
		<pubDate>Thu, 01 Mar 2007 18:56:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23497</guid>
		<description>If the net/web ever transform to something passing blocks of data rather than packets between end-points (kind of like distributed hash table-overlay networks of today) I guess URN, resolved to SHA identifiers for a suitable representation by some google-like service who parses RDF webs, would be better than direct SHAs.</description>
		<content:encoded><![CDATA[<p>If the net/web ever transform to something passing blocks of data rather than packets between end-points (kind of like distributed hash table-overlay networks of today) I guess URN, resolved to SHA identifiers for a suitable representation by some google-like service who parses RDF webs, would be better than direct SHAs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BillG</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23325</link>
		<dc:creator>BillG</dc:creator>
		<pubDate>Tue, 27 Feb 2007 00:36:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-23325</guid>
		<description>Great post.

I'm glad that you said "_Try_ to avoid request parameters" (empahasis on try), since I see this as an example of where the ideals of REST taken to the extreme would make life a real pain in the ass. I "try" to do this when desining REST protocols, but only up to a certain point. Query strings are a practical convenience and are so broadly supported that to force every URL to be in the form /foo/bar/foo2/bar2/abc/def would just make things a lot harder than they need to be (for both clients and servers).</description>
		<content:encoded><![CDATA[<p>Great post.</p>
<p>I&#8217;m glad that you said &#8220;_Try_ to avoid request parameters&#8221; (empahasis on try), since I see this as an example of where the ideals of REST taken to the extreme would make life a real pain in the ass. I &#8220;try&#8221; to do this when desining REST protocols, but only up to a certain point. Query strings are a practical convenience and are so broadly supported that to force every URL to be in the form /foo/bar/foo2/bar2/abc/def would just make things a lot harder than they need to be (for both clients and servers).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ebyblog &#187; Blog Archive &#187; Bookmarks for February 17th through February 21st</title>
		<link>http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-22974</link>
		<dc:creator>ebyblog &#187; Blog Archive &#187; Bookmarks for February 17th through February 21st</dc:creator>
		<pubDate>Thu, 22 Feb 2007 00:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.megginson.com/blogs/quoderat/2007/02/15/rest-the-quick-pitch/#comment-22974</guid>
		<description>[...] Megginson Technologies: Quoderat » Blog Archive » REST: the quick pitch - With REST, every piece of information has its own URL. [...]</description>
		<content:encoded><![CDATA[<p>[...] Megginson Technologies: Quoderat » Blog Archive » REST: the quick pitch - With REST, every piece of information has its own URL. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
