<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: RESTful Versioning</title>
	<atom:link href="http://eikonne.wordpress.com/2008/05/30/restful-versioning/feed/" rel="self" type="application/rss+xml" />
	<link>http://eikonne.wordpress.com/2008/05/30/restful-versioning/</link>
	<description>All and sundry</description>
	<lastBuildDate>Mon, 17 Aug 2009 03:35:06 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mike Amundsen</title>
		<link>http://eikonne.wordpress.com/2008/05/30/restful-versioning/#comment-40</link>
		<dc:creator>Mike Amundsen</dc:creator>
		<pubDate>Fri, 30 May 2008 16:58:06 +0000</pubDate>
		<guid isPermaLink="false">http://eikonne.wordpress.com/?p=38#comment-40</guid>
		<description>Yep, I&#039;ve come to the same result. media-types are the most reliable way to control versioning.  My approach for the &#039;human client&#039; (text/html) has been to automatically upgrade to the most recent version by mapping the custom media type and the text/html media type to the same resources.</description>
		<content:encoded><![CDATA[<p>Yep, I&#8217;ve come to the same result. media-types are the most reliable way to control versioning.  My approach for the &#8216;human client&#8217; (text/html) has been to automatically upgrade to the most recent version by mapping the custom media type and the text/html media type to the same resources.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
