<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Rails is Web Architecture Friendly</title>
	<link>http://www.semergence.com/2006/04/24/rails-is-web-architecture-friendly/</link>
	<description>Semantic Web, Ruby on Rails, and Massive Data</description>
	<pubDate>Fri, 21 Nov 2008 00:47:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: sethladd</title>
		<link>http://www.semergence.com/2006/04/24/rails-is-web-architecture-friendly/#comment-120</link>
		<dc:creator>sethladd</dc:creator>
		<pubDate>Mon, 19 Jun 2006 10:51:33 +0000</pubDate>
		<guid>http://www.semergence.com/2006/04/24/rails-is-web-architecture-friendly/#comment-120</guid>
		<description>That's probably a matter of taste.  According to http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html, the PUT method can create a new resource at the specified URI.  As long as the server allows for that, of course.  POST can be used to create a resource, if the URI that you are posting to follows the semantics of some sort of container.  No doubt, you can use either to create a new resource.  With POST, though, the server is responsible for the creation of the URI.  With PUT, the client is responsible, and it usually not in a position to create a good URI.</description>
		<content:encoded><![CDATA[<p>That&#8217;s probably a matter of taste.  According to <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html," rel="nofollow">http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html,</a> the PUT method can create a new resource at the specified URI.  As long as the server allows for that, of course.  POST can be used to create a resource, if the URI that you are posting to follows the semantics of some sort of container.  No doubt, you can use either to create a new resource.  With POST, though, the server is responsible for the creation of the URI.  With PUT, the client is responsible, and it usually not in a position to create a good URI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Henry Story</title>
		<link>http://www.semergence.com/2006/04/24/rails-is-web-architecture-friendly/#comment-119</link>
		<dc:creator>Henry Story</dc:creator>
		<pubDate>Mon, 19 Jun 2006 07:22:39 +0000</pubDate>
		<guid>http://www.semergence.com/2006/04/24/rails-is-web-architecture-friendly/#comment-119</guid>
		<description>not quite right. You madify a resource with PUT, and create a resource with POST. You delete a resource with DELETE

Henry</description>
		<content:encoded><![CDATA[<p>not quite right. You madify a resource with PUT, and create a resource with POST. You delete a resource with DELETE</p>
<p>Henry</p>
]]></content:encoded>
	</item>
</channel>
</rss>
