<?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: RailsConf: Create, Read, Update, Delete: Normalize</title>
	<atom:link href="http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/feed/" rel="self" type="application/rss+xml" />
	<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/</link>
	<description></description>
	<pubDate>Sat, 05 Jul 2008 21:12:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Fingerprints of Casper Fabricius &#187; RailsConf: People I met</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-115</link>
		<dc:creator>Fingerprints of Casper Fabricius &#187; RailsConf: People I met</dc:creator>
		<pubDate>Sat, 22 Jul 2006 23:06:14 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-115</guid>
		<description>[...] RailsConf was a blast. But I barely had the time to consume all the impressions, since my vacation was just after the event in Chicago. So I went directly to Roskilde Festival, North Europes biggest festival with 100.000 partying people near Copenhagen, Denmark, and from there I got on a bus to Rumania as part of choir singing Danish songs in the Rumanian churches. When I got back, I realized my blog had gained quite a lot of attention (at least compared to it&#8217;s very silent past), not at least my posts on David Heinemeier Hansson&#8217;s and Paul Graham&#8217;s key notes. While 70 subscribers and 200 visitors a day doesn&#8217;t sound like much to some, it fills me with a certain amount of humility: &#8220;Surely people will expect my future to be of high professional quality and deep insight&#8221;, I think. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] RailsConf was a blast. But I barely had the time to consume all the impressions, since my vacation was just after the event in Chicago. So I went directly to Roskilde Festival, North Europes biggest festival with 100.000 partying people near Copenhagen, Denmark, and from there I got on a bus to Rumania as part of choir singing Danish songs in the Rumanian churches. When I got back, I realized my blog had gained quite a lot of attention (at least compared to it&#8217;s very silent past), not at least my posts on David Heinemeier Hansson&#8217;s and Paul Graham&#8217;s key notes. While 70 subscribers and 200 visitors a day doesn&#8217;t sound like much to some, it fills me with a certain amount of humility: &#8220;Surely people will expect my future to be of high professional quality and deep insight&#8221;, I think. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Refactoring a Rails app to be RESTful</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-101</link>
		<dc:creator>Refactoring a Rails app to be RESTful</dc:creator>
		<pubDate>Fri, 21 Jul 2006 11:34:25 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-101</guid>
		<description>[...] RailsConf: Create, Read, Update, Delete: Normalize [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] RailsConf: Create, Read, Update, Delete: Normalize [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kamil Kukura</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-37</link>
		<dc:creator>Kamil Kukura</dc:creator>
		<pubDate>Sun, 09 Jul 2006 05:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-37</guid>
		<description>Well, browsers don't support 's method to be anything else from "get" or "post" because HTML 4.01 says so by the way: http://www.w3.org/TR/html4/interact/forms.html#submit-format

This is, however, different for XForms where "put" is allowed but "delete" is not. Logically, deletion of resource is identified purerly by request-uri and as that should be specified in &lt;a&gt;nchor element which is now by specs not possible.</description>
		<content:encoded><![CDATA[<p>Well, browsers don&#8217;t support &#8217;s method to be anything else from &#8220;get&#8221; or &#8220;post&#8221; because HTML 4.01 says so by the way: <a href="http://www.w3.org/TR/html4/interact/forms.html#submit-format" rel="nofollow">http://www.w3.org/TR/html4/interact/forms.html#submit-format</a></p>
<p>This is, however, different for XForms where &#8220;put&#8221; is allowed but &#8220;delete&#8221; is not. Logically, deletion of resource is identified purerly by request-uri and as that should be specified in <a>nchor element which is now by specs not possible.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dysfunksional.monkey</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-32</link>
		<dc:creator>dysfunksional.monkey</dc:creator>
		<pubDate>Tue, 04 Jul 2006 14:03:53 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-32</guid>
		<description>Thanks Casper. Just a little worried as I've seen these comments in more than one place at the moment, and if I've interpreted it correctly then it looks as though the  Rails camp is getting things wrong, which could be costly in the future.</description>
		<content:encoded><![CDATA[<p>Thanks Casper. Just a little worried as I&#8217;ve seen these comments in more than one place at the moment, and if I&#8217;ve interpreted it correctly then it looks as though the  Rails camp is getting things wrong, which could be costly in the future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Casper Fabricius</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-31</link>
		<dc:creator>Casper Fabricius</dc:creator>
		<pubDate>Sat, 01 Jul 2006 12:13:11 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-31</guid>
		<description>&lt;b&gt;dysfunksional.monkey&lt;/b&gt;
I haven't really studied the spec that much in detail, I'm just repeating what DHH said at the key note. Maybe he got it wrong - you should probably take that up with him.

&lt;b&gt;Aníbal Rojas&lt;/b&gt;
Thanks. I've registered my blog and set up the ping

&lt;b&gt;Tony&lt;/b&gt;
Guess I shouldn't do spell in Word, seems to mess up my links. Thanks, they should be fixed now.</description>
		<content:encoded><![CDATA[<p><b>dysfunksional.monkey</b><br />
I haven&#8217;t really studied the spec that much in detail, I&#8217;m just repeating what DHH said at the key note. Maybe he got it wrong - you should probably take that up with him.</p>
<p><b>Aníbal Rojas</b><br />
Thanks. I&#8217;ve registered my blog and set up the ping</p>
<p><b>Tony</b><br />
Guess I shouldn&#8217;t do spell in Word, seems to mess up my links. Thanks, they should be fixed now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olle Jonsson&#8217;s Morningstar &#187; HTTP verbs and Rails</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-30</link>
		<dc:creator>Olle Jonsson&#8217;s Morningstar &#187; HTTP verbs and Rails</dc:creator>
		<pubDate>Fri, 30 Jun 2006 08:19:08 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-30</guid>
		<description>[...] I said I was interested in talking a bit about Rails&#8217; new direction wrt HTTP verbs: it seems Casper Fabricius and the web has most of the information at hand: so enjoy Casper&#8217;s introduction to the new concepts. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] I said I was interested in talking a bit about Rails&#8217; new direction wrt HTTP verbs: it seems Casper Fabricius and the web has most of the information at hand: so enjoy Casper&#8217;s introduction to the new concepts. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dysfunksional.monkey</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-29</link>
		<dc:creator>dysfunksional.monkey</dc:creator>
		<pubDate>Thu, 29 Jun 2006 18:49:36 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-29</guid>
		<description>Sorry, copied/pasted my comment from here: http://jimonwebgames.com/articles/2006/06/26/dont-say-crud-say-fucd - hence the "dysfunksional.monkey said 3 days later:".</description>
		<content:encoded><![CDATA[<p>Sorry, copied/pasted my comment from here: <a href="http://jimonwebgames.com/articles/2006/06/26/dont-say-crud-say-fucd" rel="nofollow">http://jimonwebgames.com/articles/2006/06/26/dont-say-crud-say-fucd</a> - hence the &#8220;dysfunksional.monkey said 3 days later:&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dysfunksional.monkey</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-28</link>
		<dc:creator>dysfunksional.monkey</dc:creator>
		<pubDate>Thu, 29 Jun 2006 18:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-28</guid>
		<description>dysfunksional.monkey  said 3 days later:
Regarding the REST methods, are you sure that POST is create and PUT is update? After reading the spec (http://www.faqs.org/rfcs/rfc2616) I came to the conclusion that its the other way round, in that PUT creates a resource (returning 201 on create or 200 on replace) whereas POST handles updates (things such as "Annotation of existing resources") returning 200 on success or, if the update also creates a resource, a 201 header which should "contain an entity which describes the status of the request and refers to the new resource, and a Location header". Am I wrong?</description>
		<content:encoded><![CDATA[<p>dysfunksional.monkey  said 3 days later:<br />
Regarding the REST methods, are you sure that POST is create and PUT is update? After reading the spec (http://www.faqs.org/rfcs/rfc2616) I came to the conclusion that its the other way round, in that PUT creates a resource (returning 201 on create or 200 on replace) whereas POST handles updates (things such as &#8220;Annotation of existing resources&#8221;) returning 200 on success or, if the update also creates a resource, a 201 header which should &#8220;contain an entity which describes the status of the request and refers to the new resource, and a Location header&#8221;. Am I wrong?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aníbal Rojas</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-27</link>
		<dc:creator>Aníbal Rojas</dc:creator>
		<pubDate>Wed, 28 Jun 2006 23:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-27</guid>
		<description>First thank for this excelent review of DHH key note, REST is a really interesting "technology" and it is interesting the way it will be integrated into Rails. Second, and Off Topic: Please register you blog at RubyCorner.com (and remenber to configure the ping ;-) it is a meeting place for people interested in the Ruby Programming Language or any of the related technologies.</description>
		<content:encoded><![CDATA[<p>First thank for this excelent review of DHH key note, REST is a really interesting &#8220;technology&#8221; and it is interesting the way it will be integrated into Rails. Second, and Off Topic: Please register you blog at RubyCorner.com (and remenber to configure the ping ;-) it is a meeting place for people interested in the Ruby Programming Language or any of the related technologies.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-26</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Wed, 28 Jun 2006 16:29:01 +0000</pubDate>
		<guid isPermaLink="false">http://casperfabricius.com/blog/2006/06/25/railsconf-dhh/#comment-26</guid>
		<description>Check your links... the ones to "REST", "Normal Form" and "http protocol" are messed up.</description>
		<content:encoded><![CDATA[<p>Check your links&#8230; the ones to &#8220;REST&#8221;, &#8220;Normal Form&#8221; and &#8220;http protocol&#8221; are messed up.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
