<?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: twitter!</title>
	<atom:link href="http://mituzas.lt/2009/03/25/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://mituzas.lt/2009/03/25/twitter/</link>
	<description></description>
	<lastBuildDate>Fri, 30 Jul 2010 21:52:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1-alpha</generator>
	<item>
		<title>By: twitter! « domas mituzas: vaporware, inc. &#124; Twitter Kid</title>
		<link>http://mituzas.lt/2009/03/25/twitter/comment-page-1/#comment-189052</link>
		<dc:creator>twitter! « domas mituzas: vaporware, inc. &#124; Twitter Kid</dc:creator>
		<pubDate>Mon, 30 Mar 2009 22:24:21 +0000</pubDate>
		<guid isPermaLink="false">http://dammit.lt/?p=436#comment-189052</guid>
		<description>[...] original post here:  twitter! « domas mituzas: vaporware, inc.      Posted in Articles &#124;  Tags: 2009-at-2143, amazon, browser, europe, expires, firefox, march-26, [...]</description>
		<content:encoded><![CDATA[<p>[...] original post here:  twitter! « domas mituzas: vaporware, inc.      Posted in Articles |  Tags: 2009-at-2143, amazon, browser, europe, expires, firefox, march-26, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco</title>
		<link>http://mituzas.lt/2009/03/25/twitter/comment-page-1/#comment-189045</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Sun, 29 Mar 2009 19:43:37 +0000</pubDate>
		<guid isPermaLink="false">http://dammit.lt/?p=436#comment-189045</guid>
		<description>Thank you for the expiration date hint, but a lot of traffic is produced via API and not just the web interface. xD</description>
		<content:encoded><![CDATA[<p>Thank you for the expiration date hint, but a lot of traffic is produced via API and not just the web interface. xD</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Saliem</title>
		<link>http://mituzas.lt/2009/03/25/twitter/comment-page-1/#comment-189032</link>
		<dc:creator>Saliem</dc:creator>
		<pubDate>Thu, 26 Mar 2009 21:04:32 +0000</pubDate>
		<guid isPermaLink="false">http://dammit.lt/?p=436#comment-189032</guid>
		<description>is that why you don&#039;t have a twitter account? :D</description>
		<content:encoded><![CDATA[<p>is that why you don&#8217;t have a twitter account? :D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Lintz</title>
		<link>http://mituzas.lt/2009/03/25/twitter/comment-page-1/#comment-189029</link>
		<dc:creator>Justin Lintz</dc:creator>
		<pubDate>Wed, 25 Mar 2009 23:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://dammit.lt/?p=436#comment-189029</guid>
		<description>Including an ETag won&#039;t do much of anything if they have an Expires and max-age already set.  With just an ETag set , anytime a repeat visitor hits a page with a static asset already cached, it will send a INM request, and the server will respond with a 304.  If you have just the expires or max-age set, the browser won&#039;t even re-validate the object, it will just serve from the browser cache, saving on some bandwidth.  

I don&#039;t think adding public to cache-control would affect anything either as that IIRC just makes http authenticated responses cachable.</description>
		<content:encoded><![CDATA[<p>Including an ETag won&#8217;t do much of anything if they have an Expires and max-age already set.  With just an ETag set , anytime a repeat visitor hits a page with a static asset already cached, it will send a INM request, and the server will respond with a 304.  If you have just the expires or max-age set, the browser won&#8217;t even re-validate the object, it will just serve from the browser cache, saving on some bandwidth.  </p>
<p>I don&#8217;t think adding public to cache-control would affect anything either as that IIRC just makes http authenticated responses cachable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Domas Mituzas</title>
		<link>http://mituzas.lt/2009/03/25/twitter/comment-page-1/#comment-189028</link>
		<dc:creator>Domas Mituzas</dc:creator>
		<pubDate>Wed, 25 Mar 2009 23:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://dammit.lt/?p=436#comment-189028</guid>
		<description>well, we use Vary at Wikipedia a lot, and it doesn&#039;t seem to be causing any caching problems (as long, as we handle the remaining set of headers properly).</description>
		<content:encoded><![CDATA[<p>well, we use Vary at Wikipedia a lot, and it doesn&#8217;t seem to be causing any caching problems (as long, as we handle the remaining set of headers properly).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh Davis</title>
		<link>http://mituzas.lt/2009/03/25/twitter/comment-page-1/#comment-189027</link>
		<dc:creator>Josh Davis</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:56:29 +0000</pubDate>
		<guid isPermaLink="false">http://dammit.lt/?p=436#comment-189027</guid>
		<description>The culprit here must be the Vary header. Most browsers interpret it as &quot;Cache-control: must-revalidate&quot; no matter what other headers you sent with. In fact, I&#039;ve just tested twitter.com on my Firefox 3.0.7 and the CSS files don&#039;t even seem to be cached at all.</description>
		<content:encoded><![CDATA[<p>The culprit here must be the Vary header. Most browsers interpret it as &#8220;Cache-control: must-revalidate&#8221; no matter what other headers you sent with. In fact, I&#8217;ve just tested twitter.com on my Firefox 3.0.7 and the CSS files don&#8217;t even seem to be cached at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Markauskas</title>
		<link>http://mituzas.lt/2009/03/25/twitter/comment-page-1/#comment-189026</link>
		<dc:creator>Tomas Markauskas</dc:creator>
		<pubDate>Wed, 25 Mar 2009 22:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://dammit.lt/?p=436#comment-189026</guid>
		<description>They could at least use Amazon&#039;s CloudFront as a CDN which is so easy to implement. Proper timestamps for assets would probably save them more than a lunch in data transfer fees :)</description>
		<content:encoded><![CDATA[<p>They could at least use Amazon&#8217;s CloudFront as a CDN which is so easy to implement. Proper timestamps for assets would probably save them more than a lunch in data transfer fees :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
