<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BigSmoke &#187; REST</title>
	<atom:link href="http://blog.bigsmoke.us/tag/rest/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.bigsmoke.us</link>
	<description>Smokes your problems, coughs fresh air.</description>
	<lastBuildDate>Sat, 04 Feb 2012 18:03:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Atom and REST</title>
		<link>http://blog.bigsmoke.us/2009/10/09/atom-rest</link>
		<comments>http://blog.bigsmoke.us/2009/10/09/atom-rest#comments</comments>
		<pubDate>Fri, 09 Oct 2009 21:07:17 +0000</pubDate>
		<dc:creator>Rowan Rodrik</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[Atom]]></category>
		<category><![CDATA[HTTP]]></category>
		<category><![CDATA[REST]]></category>

		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=841</guid>
		<description><![CDATA[]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s is an interesting discussion about <a href="http://bill.burkecentral.com/2008/10/06/atom-too-soapy-for-me/">when (not) to use the Atom protocol for your REST API</a>.</p>

<p>While looking at the trackbacks of that post, I came across a very nice post by Subbu detailing the <a href="http://www.subbu.org/blog/2008/10/location-vs-content-location">differences between and uses of the <tt>Location</tt> and <tt>Content-Location</tt> HTTP headers</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://blog.bigsmoke.us/2009/10/09/atom-rest/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

