<?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: RESTful Rails. Part I</title>
	<atom:link href="http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/</link>
	<description>News, opinion, and fresh thinking for web developers and designers. The official podcast of sitepoint.com.</description>
	<lastBuildDate>Sun, 22 Nov 2009 11:54:05 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: madpilot</title>
		<link>http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/comment-page-1/#comment-631761</link>
		<dc:creator>madpilot</dc:creator>
		<pubDate>Sun, 10 Feb 2008 23:22:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/#comment-631761</guid>
		<description>vSkyfluxx: I&#039;m going to go through the specifics of the Rails REST implementation in my next post.

Thanks</description>
		<content:encoded><![CDATA[<p>vSkyfluxx: I&#8217;m going to go through the specifics of the Rails REST implementation in my next post.</p>
<p>Thanks</p>]]></content:encoded>
	</item>
	<item>
		<title>By: vSkyfluxx</title>
		<link>http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/comment-page-1/#comment-631750</link>
		<dc:creator>vSkyfluxx</dc:creator>
		<pubDate>Sun, 10 Feb 2008 22:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/#comment-631750</guid>
		<description>It might not be a bad idea to also include the &quot;new&quot; and &quot;edit&quot; actions in your resources table.</description>
		<content:encoded><![CDATA[<p>It might not be a bad idea to also include the &#8220;new&#8221; and &#8220;edit&#8221; actions in your resources table.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: tndalpaul</title>
		<link>http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/comment-page-1/#comment-628949</link>
		<dc:creator>tndalpaul</dc:creator>
		<pubDate>Thu, 07 Feb 2008 07:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/#comment-628949</guid>
		<description>There&#039;s been considerable discussion whether  POST or PUT should handle creation or update. For example see 
http://www.megginson.com/blogs/quoderat/2005/04/03/post-in-rest-create-update-or-action/

wherein, for example, Mark Baker Says: 
&gt; April 4th, 2005 at 10:56:16 
&gt; FWIW, both POST and PUT can do creation; PUT &gt; for when the client knows the URI of the 
&gt; thing it’s trying to create, and POST for 
&gt; when it doesn’t.</description>
		<content:encoded><![CDATA[<p>There&#8217;s been considerable discussion whether  POST or PUT should handle creation or update. For example see<br />
<a href="http://www.megginson.com/blogs/quoderat/2005/04/03/post-in-rest-create-update-or-action/" rel="nofollow">http://www.megginson.com/blogs/quoderat/2005/04/03/post-in-rest-create-update-or-action/</a></p>
<p>wherein, for example, Mark Baker Says:<br />
&gt; April 4th, 2005 at 10:56:16<br />
&gt; FWIW, both POST and PUT can do creation; PUT &gt; for when the client knows the URI of the<br />
&gt; thing it’s trying to create, and POST for<br />
&gt; when it doesn’t.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: madpilot</title>
		<link>http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/comment-page-1/#comment-623538</link>
		<dc:creator>madpilot</dc:creator>
		<pubDate>Mon, 04 Feb 2008 07:16:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/#comment-623538</guid>
		<description>Thanks for the correction, Paul. You are 100% correct.</description>
		<content:encoded><![CDATA[<p>Thanks for the correction, Paul. You are 100% correct.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Annesley</title>
		<link>http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/comment-page-1/#comment-623536</link>
		<dc:creator>Paul Annesley</dc:creator>
		<pubDate>Mon, 04 Feb 2008 07:12:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.sitepoint.com/blogs/2008/02/04/restful-rails-part-i/#comment-623536</guid>
		<description>It&#039;s probably worth noting that POST and PUT requests send their data in the body of the request - after the headers, not in them.  It&#039;ll make little or no practical difference to most users, but might trip somebody up.</description>
		<content:encoded><![CDATA[<p>It&#8217;s probably worth noting that POST and PUT requests send their data in the body of the request &#8211; after the headers, not in them.  It&#8217;ll make little or no practical difference to most users, but might trip somebody up.</p>]]></content:encoded>
	</item>
</channel>
</rss>
