<?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: Cloudfront: no-brainer CDN support for S3</title>
	<atom:link href="http://trevorturk.wordpress.com/2010/02/08/cloudfront-no-brainer-cdn-support-for-s3/feed/" rel="self" type="application/rss+xml" />
	<link>http://trevorturk.wordpress.com/2010/02/08/cloudfront-no-brainer-cdn-support-for-s3/</link>
	<description>A chess-playing machine of the late 18th century, promoted as an automaton but later proved a hoax.</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:13:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Trevor Turk &#8212; Caching assets in a Rails 3 app on Heroku</title>
		<link>http://trevorturk.wordpress.com/2010/02/08/cloudfront-no-brainer-cdn-support-for-s3/#comment-906</link>
		<dc:creator><![CDATA[Trevor Turk &#8212; Caching assets in a Rails 3 app on Heroku]]></dc:creator>
		<pubDate>Tue, 18 Jan 2011 12:35:57 +0000</pubDate>
		<guid isPermaLink="false">http://almosteffortless.com/?p=1688#comment-906</guid>
		<description><![CDATA[[...] and upload them to S3, using CloudFront as a CDN, and telling Rails to use that as your asset host. I&#8217;ve talked about CloudFront before, and I&#8217;ve had nothing but positive experiences with it, so I might try this in the future [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] and upload them to S3, using CloudFront as a CDN, and telling Rails to use that as your asset host. I&#8217;ve talked about CloudFront before, and I&#8217;ve had nothing but positive experiences with it, so I might try this in the future [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

