<?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: Amazon CloudFront: Simple Caching and Naming</title>
	<atom:link href="http://www.redmonk.com/jgovernor/2008/11/28/amazon-cloudfront-simple-caching-and-naming/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/jgovernor/2008/11/28/amazon-cloudfront-simple-caching-and-naming/</link>
	<description>An industry analyst blog looking at software ecosystems and convergence</description>
	<lastBuildDate>Fri, 03 Feb 2012 10:35:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Matt Biddulph</title>
		<link>http://www.redmonk.com/jgovernor/2008/11/28/amazon-cloudfront-simple-caching-and-naming/comment-page-1/#comment-504590</link>
		<dc:creator>Matt Biddulph</dc:creator>
		<pubDate>Fri, 05 Dec 2008 14:21:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/?p=1709#comment-504590</guid>
		<description>jalegre,

We don&#039;t worry about updates to files at Dopplr: we just generate a new ID every time we change any image (and therefore a new URL), and update our pointer to it in the database. The old versions can be cleaned up from S3 from time to time using a batch job, and we know that everyone is always seeing the latest version.</description>
		<content:encoded><![CDATA[<p>jalegre,</p>
<p>We don&#8217;t worry about updates to files at Dopplr: we just generate a new ID every time we change any image (and therefore a new URL), and update our pointer to it in the database. The old versions can be cleaned up from S3 from time to time using a batch job, and we know that everyone is always seeing the latest version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jalegre</title>
		<link>http://www.redmonk.com/jgovernor/2008/11/28/amazon-cloudfront-simple-caching-and-naming/comment-page-1/#comment-503184</link>
		<dc:creator>jalegre</dc:creator>
		<pubDate>Sun, 30 Nov 2008 12:49:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/?p=1709#comment-503184</guid>
		<description>Thanks for my link to tweeter. Nice article. After using CloudFront few days the only drawback is sometimes changes are not instant like S3.

For new content I have seen that connects to S3, gets data, and distributed.

But when trying to update a file the caching systems goes its way, and there is no way of telling CloudFront easily to update files right now, at least on S3 Organizer Firefox extension.

So if someone updates a profile photo, if you use S3 you know changes will be instant. If you use CloudFront, will be faster, but user could or could not see the uploaded picture.

And as Amazon says, if you need update a file and distribute must contact Amazon.

I guess amazon in the following months will come up with a method to say &quot;distribute now&quot; so that changes are instant on a file. They are not doing this now so their network is not saturated I imagine.</description>
		<content:encoded><![CDATA[<p>Thanks for my link to tweeter. Nice article. After using CloudFront few days the only drawback is sometimes changes are not instant like S3.</p>
<p>For new content I have seen that connects to S3, gets data, and distributed.</p>
<p>But when trying to update a file the caching systems goes its way, and there is no way of telling CloudFront easily to update files right now, at least on S3 Organizer Firefox extension.</p>
<p>So if someone updates a profile photo, if you use S3 you know changes will be instant. If you use CloudFront, will be faster, but user could or could not see the uploaded picture.</p>
<p>And as Amazon says, if you need update a file and distribute must contact Amazon.</p>
<p>I guess amazon in the following months will come up with a method to say &#8220;distribute now&#8221; so that changes are instant on a file. They are not doing this now so their network is not saturated I imagine.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

