<?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: Asynchronous HTTP Cache Validations</title>
	<atom:link href="http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/</link>
	<description>A goal is a dream with a deadline.</description>
	<pubDate>Sun, 05 Jul 2009 03:43:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ilya Grigorik</title>
		<link>http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/comment-page-1/#comment-172794</link>
		<dc:creator>Ilya Grigorik</dc:creator>
		<pubDate>Thu, 26 Feb 2009 18:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/?p=194#comment-172794</guid>
		<description>Yep, I've played around with that and it's a great feature. The only difference is that a grace period in Varnish guards against the 'dog-pile' effect, but does not actually serve up stale content on the first cache-miss. Minor difference, but one to keep in mind.</description>
		<content:encoded><![CDATA[<p>Yep, I&#8217;ve played around with that and it&#8217;s a great feature. The only difference is that a grace period in Varnish guards against the &#8216;dog-pile&#8217; effect, but does not actually serve up stale content on the first cache-miss. Minor difference, but one to keep in mind.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Perham</title>
		<link>http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/comment-page-1/#comment-172781</link>
		<dc:creator>Mike Perham</dc:creator>
		<pubDate>Thu, 26 Feb 2009 17:57:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/?p=194#comment-172781</guid>
		<description>Varnish supports a "grace period" for stale objects:

http://varnish.projects.linpro.no/wiki/Performance</description>
		<content:encoded><![CDATA[<p>Varnish supports a &#8220;grace period&#8221; for stale objects:</p>
<p><a href="http://varnish.projects.linpro.no/wiki/Performance" rel="nofollow">http://varnish.projects.linpro.no/wiki/Performance</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ilya Grigorik</title>
		<link>http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/comment-page-1/#comment-140992</link>
		<dc:creator>Ilya Grigorik</dc:creator>
		<pubDate>Thu, 16 Oct 2008 03:36:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/?p=194#comment-140992</guid>
		<description>TJ, you're right, this pattern is not for everybody, but as Nate described, for certain types of content this can be a life savior. (ex: dynamic widgets, news blocks, etc... anything that's not directly affected by user actions)

Ben, I've done a quick pass over merb-cache but did not similar pattern you're referring to. Is there a specific file I should be looking at? (I still believe this code belongs higher up in the stack).</description>
		<content:encoded><![CDATA[<p>TJ, you&#8217;re right, this pattern is not for everybody, but as Nate described, for certain types of content this can be a life savior. (ex: dynamic widgets, news blocks, etc&#8230; anything that&#8217;s not directly affected by user actions)</p>
<p>Ben, I&#8217;ve done a quick pass over merb-cache but did not similar pattern you&#8217;re referring to. Is there a specific file I should be looking at? (I still believe this code belongs higher up in the stack).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Schwarz</title>
		<link>http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/comment-page-1/#comment-140479</link>
		<dc:creator>Ben Schwarz</dc:creator>
		<pubDate>Thu, 09 Oct 2008 08:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/?p=194#comment-140479</guid>
		<description>This sounds very similar to the cache pattern that we've implemented for Merb's recent "merb-cache".

Read more about &lt;a href="http://merbunity.com/tutorials/15" rel="nofollow"&gt;how to get running with merb-cache&lt;/a&gt; or &lt;a href="http://github.com/wycats/merb-more/tree/master/merb-cache" rel="nofollow"&gt;watch the progress on github&lt;/a&gt;

Cache strategies can be mixed, matched and even joined together, this; with 'eager cache' and you've got yourself a very agile content distribution system.</description>
		<content:encoded><![CDATA[<p>This sounds very similar to the cache pattern that we&#8217;ve implemented for Merb&#8217;s recent &#8220;merb-cache&#8221;.</p>
<p>Read more about <a href="http://merbunity.com/tutorials/15" rel="nofollow">how to get running with merb-cache</a> or <a href="http://github.com/wycats/merb-more/tree/master/merb-cache" rel="nofollow">watch the progress on github</a></p>
<p>Cache strategies can be mixed, matched and even joined together, this; with &#8216;eager cache&#8217; and you&#8217;ve got yourself a very agile content distribution system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2008-10-08 &#171; Bloggitation</title>
		<link>http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/comment-page-1/#comment-140282</link>
		<dc:creator>links for 2008-10-08 &#171; Bloggitation</dc:creator>
		<pubDate>Wed, 08 Oct 2008 08:35:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/?p=194#comment-140282</guid>
		<description>[...] Asynchronous HTTP Cache Validations (tags: ruby rails cluster memcached 247up programming) [...]</description>
		<content:encoded><![CDATA[<p>[...] Asynchronous HTTP Cache Validations (tags: ruby rails cluster memcached 247up programming) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nate</title>
		<link>http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/comment-page-1/#comment-140080</link>
		<dc:creator>Nate</dc:creator>
		<pubDate>Tue, 07 Oct 2008 15:03:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/?p=194#comment-140080</guid>
		<description>There are many situations where an app doesn't require real time info.  For example, the plethora of apps out there pulling news from RSS feeds for say each individual user, or individual accounts.  And too many RSS feeds take seconds to pull down from their original server.  It's such a waste to just run a cron job to refresh each users RSS feed.

Asynchronously invalidating a cache of that RSS content is a wonderful pattern for this situation.</description>
		<content:encoded><![CDATA[<p>There are many situations where an app doesn&#8217;t require real time info.  For example, the plethora of apps out there pulling news from RSS feeds for say each individual user, or individual accounts.  And too many RSS feeds take seconds to pull down from their original server.  It&#8217;s such a waste to just run a cron job to refresh each users RSS feed.</p>
<p>Asynchronously invalidating a cache of that RSS content is a wonderful pattern for this situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TJ Murphy</title>
		<link>http://www.igvita.com/2008/10/07/asynchronous-http-cache-validations/comment-page-1/#comment-140070</link>
		<dc:creator>TJ Murphy</dc:creator>
		<pubDate>Tue, 07 Oct 2008 14:19:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.igvita.com/?p=194#comment-140070</guid>
		<description>While definitely a good pattern to keep in mind, I feel that the one small caveat "if your application can afford to show slightly out of date content" makes it unusable in many situations.  With responsiveness so closely tied to usability, you'd be hard pressed to find situations to use this on the HTTP level.</description>
		<content:encoded><![CDATA[<p>While definitely a good pattern to keep in mind, I feel that the one small caveat &#8220;if your application can afford to show slightly out of date content&#8221; makes it unusable in many situations.  With responsiveness so closely tied to usability, you&#8217;d be hard pressed to find situations to use this on the HTTP level.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
