<?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: DELETE and 201 Created</title>
	<atom:link href="http://www.nordsc.com/blog/?feed=rss2&#038;p=411" rel="self" type="application/rss+xml" />
	<link>http://www.nordsc.com/blog/?p=411</link>
	<description></description>
	<lastBuildDate>Mon, 05 Jul 2010 15:38:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: jan</title>
		<link>http://www.nordsc.com/blog/?p=411#comment-349</link>
		<dc:creator>jan</dc:creator>
		<pubDate>Mon, 22 Mar 2010 21:12:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.nordsc.com/blog/?p=411#comment-349</guid>
		<description>Mike,
but Location header does not indicate resource creation. The meaning of the Location header depends on the status.</description>
		<content:encoded><![CDATA[<p>Mike,<br />
but Location header does not indicate resource creation. The meaning of the Location header depends on the status.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Amundsen</title>
		<link>http://www.nordsc.com/blog/?p=411#comment-345</link>
		<dc:creator>Mike Amundsen</dc:creator>
		<pubDate>Mon, 22 Mar 2010 17:40:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.nordsc.com/blog/?p=411#comment-345</guid>
		<description>IMO, 201 is a confusing response.  200 or 204 w/ a Location header is just as handy.</description>
		<content:encoded><![CDATA[<p>IMO, 201 is a confusing response.  200 or 204 w/ a Location header is just as handy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Banwart&#39;s Blog &#187; Blog Archive &#187; Distributed Weekly 41</title>
		<link>http://www.nordsc.com/blog/?p=411#comment-246</link>
		<dc:creator>Scott Banwart&#39;s Blog &#187; Blog Archive &#187; Distributed Weekly 41</dc:creator>
		<pubDate>Fri, 12 Mar 2010 15:38:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.nordsc.com/blog/?p=411#comment-246</guid>
		<description>[...] DELETE and 201 Created [...]</description>
		<content:encoded><![CDATA[<p>[...] DELETE and 201 Created [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Cummings</title>
		<link>http://www.nordsc.com/blog/?p=411#comment-173</link>
		<dc:creator>Steven Cummings</dc:creator>
		<pubDate>Tue, 09 Mar 2010 02:30:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.nordsc.com/blog/?p=411#comment-173</guid>
		<description>Interesting, I had a similar thought. What I came up with is that, although the resource has been deleted, the URI redirects to the new archive entry instead of resulting in 410 GONE (or plain old 404).</description>
		<content:encoded><![CDATA[<p>Interesting, I had a similar thought. What I came up with is that, although the resource has been deleted, the URI redirects to the new archive entry instead of resulting in 410 GONE (or plain old 404).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: This Week in REST – Volume 6 (Mar 1 2010 – Mar 7 2010) &#171; This week in REST</title>
		<link>http://www.nordsc.com/blog/?p=411#comment-171</link>
		<dc:creator>This Week in REST – Volume 6 (Mar 1 2010 – Mar 7 2010) &#171; This week in REST</dc:creator>
		<pubDate>Mon, 08 Mar 2010 09:21:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.nordsc.com/blog/?p=411#comment-171</guid>
		<description>[...] protocol &#8211; The latest update to the REST-* Message draft specification. (by Bill Burke) DELETE and 201 Created &#8211; An interesting way to combine the DELETE verb and the 201 response. (by Jan Algermissen) [...]</description>
		<content:encoded><![CDATA[<p>[...] protocol &#8211; The latest update to the REST-* Message draft specification. (by Bill Burke) DELETE and 201 Created &#8211; An interesting way to combine the DELETE verb and the 201 response. (by Jan Algermissen) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
