<?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: Idea about Expires header</title>
	<atom:link href="http://hauru.eu/2009/10/18/idea-about-expires-header/feed/" rel="self" type="application/rss+xml" />
	<link>http://hauru.eu/2009/10/18/idea-about-expires-header/</link>
	<description>Personal techblog by Tomek Paczkowski</description>
	<lastBuildDate>Thu, 25 Mar 2010 08:08:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: kwalo</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-1828</link>
		<dc:creator>kwalo</dc:creator>
		<pubDate>Thu, 25 Mar 2010 08:08:11 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-1828</guid>
		<description>Yet another recipe to serve static media in Django: http://www.peterbe.com/plog/serve-your-static-stuff-in-django-with-nginx</description>
		<content:encoded><![CDATA[<p>Yet another recipe to serve static media in Django: <a href="http://www.peterbe.com/plog/serve-your-static-stuff-in-django-with-nginx" rel="nofollow">http://www.peterbe.com/plog/serve-your-static-stuff-in-django-with-nginx</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-1326</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Wed, 17 Feb 2010 10:51:16 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-1326</guid>
		<description>We went with versioning the path and updating it based on the revision number in a Subversion repository.  There&#039;s different ways to do it, but this is automatic and working well for us

&lt;a href=&quot;http://www.redrobotstudios.com/blog/2008/12/18/versioned-media-and-expires-headers-in-django/&quot; rel=&quot;nofollow&quot;&gt;http://www.redrobotstudios.com/blog/2008/12/18/versioned-media-and-expires-headers-in-django/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>We went with versioning the path and updating it based on the revision number in a Subversion repository.  There&#8217;s different ways to do it, but this is automatic and working well for us</p>
<p><a href="http://www.redrobotstudios.com/blog/2008/12/18/versioned-media-and-expires-headers-in-django/" rel="nofollow">http://www.redrobotstudios.com/blog/2008/12/18/versioned-media-and-expires-headers-in-django/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oinopion</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-478</link>
		<dc:creator>oinopion</dc:creator>
		<pubDate>Mon, 02 Nov 2009 00:57:46 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-478</guid>
		<description>Nice to hear that!</description>
		<content:encoded><![CDATA[<p>Nice to hear that!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pstradomski</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-477</link>
		<dc:creator>pstradomski</dc:creator>
		<pubDate>Sun, 01 Nov 2009 23:58:40 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-477</guid>
		<description>Tried it on the development version of KSM site (though with url prefix, not domain prefix). Works like a charm - most pages now require just a single request to fetch HTML, everything else is cached.</description>
		<content:encoded><![CDATA[<p>Tried it on the development version of KSM site (though with url prefix, not domain prefix). Works like a charm &#8211; most pages now require just a single request to fetch HTML, everything else is cached.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oinopion</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-458</link>
		<dc:creator>oinopion</dc:creator>
		<pubDate>Wed, 21 Oct 2009 22:03:23 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-458</guid>
		<description>Editing URLs by hand is tedious and can be forgotten (especially when one image is used in many places). Passing it to VCS hook requires writing some more or less sophisticated script and that&#039;s as good as writing patch for Less (CSS preprocessor) to do that. And yes, my solution would force downloading every component after one change. I don&#039;t say your hints are bad or my solution is better, it just happens that I have different priorities.</description>
		<content:encoded><![CDATA[<p>Editing URLs by hand is tedious and can be forgotten (especially when one image is used in many places). Passing it to VCS hook requires writing some more or less sophisticated script and that&#8217;s as good as writing patch for Less (CSS preprocessor) to do that. And yes, my solution would force downloading every component after one change. I don&#8217;t say your hints are bad or my solution is better, it just happens that I have different priorities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mekk</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-457</link>
		<dc:creator>Mekk</dc:creator>
		<pubDate>Wed, 21 Oct 2009 15:19:53 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-457</guid>
		<description>I am just patching URLs manually when appropriate (linking to 
/some/thing-13.png or /other/style-21.css and using nginx rewrite rule to strip -(\d ) from static files), and don&#039;t find it too troublesome, but I guess it depends on the application. 

Your idea is interesting, but I find one drawback. When does this number in domain name change? If it is common for all files, then even resources which were not changed would need to be redownloaded. If it is different for every image/file, then there are no chances for keepalive connection, and the browser may hog your server as the limit of 2 connections to one address does not apply.

PS There always is a possibility to patch the urls using version control hooks or build script hooks....</description>
		<content:encoded><![CDATA[<p>I am just patching URLs manually when appropriate (linking to<br />
/some/thing-13.png or /other/style-21.css and using nginx rewrite rule to strip -(\d ) from static files), and don&#8217;t find it too troublesome, but I guess it depends on the application. </p>
<p>Your idea is interesting, but I find one drawback. When does this number in domain name change? If it is common for all files, then even resources which were not changed would need to be redownloaded. If it is different for every image/file, then there are no chances for keepalive connection, and the browser may hog your server as the limit of 2 connections to one address does not apply.</p>
<p>PS There always is a possibility to patch the urls using version control hooks or build script hooks&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oinopion</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-447</link>
		<dc:creator>oinopion</dc:creator>
		<pubDate>Mon, 19 Oct 2009 22:04:00 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-447</guid>
		<description>@lbadura: No, not yet. I&#039;ll be trying that in some time for my brand new application I&#039;m developing as my Honours Project.</description>
		<content:encoded><![CDATA[<p>@lbadura: No, not yet. I&#8217;ll be trying that in some time for my brand new application I&#8217;m developing as my Honours Project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lbadura</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-446</link>
		<dc:creator>lbadura</dc:creator>
		<pubDate>Mon, 19 Oct 2009 17:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-446</guid>
		<description>It&#039;s an interesting idea. Have you tried implementing it in one of your
applications ?</description>
		<content:encoded><![CDATA[<p>It&#8217;s an interesting idea. Have you tried implementing it in one of your<br />
applications ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: oinopion</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-444</link>
		<dc:creator>oinopion</dc:creator>
		<pubDate>Sun, 18 Oct 2009 21:14:39 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-444</guid>
		<description>I was thinking about Google App Engine (again!). GAE gives you wildcard subdomains for free and AFAIK doesn&#039;t allow synlinks. But for dedicated servers versioned path might be better.</description>
		<content:encoded><![CDATA[<p>I was thinking about Google App Engine (again!). GAE gives you wildcard subdomains for free and AFAIK doesn&#8217;t allow synlinks. But for dedicated servers versioned path might be better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pstradomski</title>
		<link>http://hauru.eu/2009/10/18/idea-about-expires-header/comment-page-1/#comment-443</link>
		<dc:creator>pstradomski</dc:creator>
		<pubDate>Sun, 18 Oct 2009 19:14:52 +0000</pubDate>
		<guid isPermaLink="false">http://hauru.eu/?p=72#comment-443</guid>
		<description>Might be easier to just version a path.

eg : /static-1234/style.css, /static-1234/image.png
and then reference the image as url(&#039;./image.png&#039;) from the stylesheet. No need for wildcard domains (which are often inaccessible).

Great idea anyway. Might try to implement it.</description>
		<content:encoded><![CDATA[<p>Might be easier to just version a path.</p>
<p>eg : /static-1234/style.css, /static-1234/image.png<br />
and then reference the image as url(&#8216;./image.png&#8217;) from the stylesheet. No need for wildcard domains (which are often inaccessible).</p>
<p>Great idea anyway. Might try to implement it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
