<?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: Nginx and Mirror on Demand</title>
	<atom:link href="http://hostingfu.com/article/nginx-and-mirror-demand/feed" rel="self" type="application/rss+xml" />
	<link>http://hostingfu.com/article/nginx-and-mirror-demand</link>
	<description>Web Hosting Blog by a Software Developer</description>
	<lastBuildDate>Mon, 15 Mar 2010 14:17:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: mike503</title>
		<link>http://hostingfu.com/article/nginx-and-mirror-demand/comment-page-1#comment-717</link>
		<dc:creator>mike503</dc:creator>
		<pubDate>Sun, 04 May 2008 09:44:42 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=125#comment-717</guid>
		<description>&lt;p&gt;I would think mainly due to the files being changed at the source...&lt;/p&gt;
&lt;p&gt;I&#039;m thinking you have something like a large RAID array, and this would be a nice way to save trips back to the source. I don&#039;t believe it actually -writes- any files unless the application can speak REST/DAV?&lt;/p&gt;
&lt;p&gt;Also you might run out of disk space on web nodes, as those typically don&#039;t have enough room for your full website&#039;s data... so you could set it up as an LRU read-through cache basically, much like memcached would be used in front of MySQL...&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I would think mainly due to the files being changed at the source&#8230;</p>
<p>I&#8217;m thinking you have something like a large RAID array, and this would be a nice way to save trips back to the source. I don&#8217;t believe it actually -writes- any files unless the application can speak REST/DAV?</p>
<p>Also you might run out of disk space on web nodes, as those typically don&#8217;t have enough room for your full website&#8217;s data&#8230; so you could set it up as an LRU read-through cache basically, much like memcached would be used in front of MySQL&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hone</title>
		<link>http://hostingfu.com/article/nginx-and-mirror-demand/comment-page-1#comment-716</link>
		<dc:creator>Hone</dc:creator>
		<pubDate>Mon, 19 Nov 2007 00:42:50 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=125#comment-716</guid>
		<description>&lt;p&gt;Why would you need to temporarily invalidate the cache?&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Why would you need to temporarily invalidate the cache?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JosephB</title>
		<link>http://hostingfu.com/article/nginx-and-mirror-demand/comment-page-1#comment-715</link>
		<dc:creator>JosephB</dc:creator>
		<pubDate>Thu, 26 Jul 2007 00:40:36 +0000</pubDate>
		<guid isPermaLink="false">http://hostingfu.com/?p=125#comment-715</guid>
		<description>&lt;p&gt;Using nginx-0.6.5 I found that the proxy_temp_path directive doesn&#039;t work.&lt;/p&gt;
&lt;p&gt;&quot;proxy_temp_path      /data/temp;&quot;&lt;/p&gt;
&lt;p&gt;this seems to be ignored and nginx uses the directive specified at compile time, by default that is /usr/local/nginx/html&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Using nginx-0.6.5 I found that the proxy_temp_path directive doesn&#8217;t work.</p>
<p>&#8220;proxy_temp_path      /data/temp;&#8221;</p>
<p>this seems to be ignored and nginx uses the directive specified at compile time, by default that is /usr/local/nginx/html</p>
]]></content:encoded>
	</item>
</channel>
</rss>
