<?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: We Have Disabled WP Super Cache</title>
	<atom:link href="http://www.cloudfour.com/we-have-disabled-wp-super-cache/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cloudfour.com/we-have-disabled-wp-super-cache/</link>
	<description>Expert Web and Mobile Design, Development and Strategy</description>
	<lastBuildDate>Wed, 08 Sep 2010 15:17:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dr. Mike Wendell</title>
		<link>http://www.cloudfour.com/we-have-disabled-wp-super-cache/comment-page-1/#comment-5541</link>
		<dc:creator>Dr. Mike Wendell</dc:creator>
		<pubDate>Sat, 13 Jun 2009 12:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/?p=253#comment-5541</guid>
		<description>You chould also step it down into half mode.  You won&#039;t get the hard coded static files but you will get the data saved and that&#039;s better than nothing.  That&#039;s what we run our WordPress Mu installs with.</description>
		<content:encoded><![CDATA[<p>You chould also step it down into half mode.  You won&#8217;t get the hard coded static files but you will get the data saved and that&#8217;s better than nothing.  That&#8217;s what we run our WordPress Mu installs with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Keith</title>
		<link>http://www.cloudfour.com/we-have-disabled-wp-super-cache/comment-page-1/#comment-5150</link>
		<dc:creator>John Keith</dc:creator>
		<pubDate>Mon, 18 May 2009 18:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/?p=253#comment-5150</guid>
		<description>Hi Thomas:

I think you are on the right track here.  Basically you are proposing an adaptive caching strategy to complement an adaptive content strategy.  I would generalize this approach to say that your caching strategy should fully accommodate your device classes.  That is, why not cache pages for each device class?  With this approach we can maximize performance for all devices at the expense of a relatively small amount of cache storage capacity.

Thank you for suggesting this line of thinking.

 - John</description>
		<content:encoded><![CDATA[<p>Hi Thomas:</p>
<p>I think you are on the right track here.  Basically you are proposing an adaptive caching strategy to complement an adaptive content strategy.  I would generalize this approach to say that your caching strategy should fully accommodate your device classes.  That is, why not cache pages for each device class?  With this approach we can maximize performance for all devices at the expense of a relatively small amount of cache storage capacity.</p>
<p>Thank you for suggesting this line of thinking.</p>
<p> &#8211; John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas</title>
		<link>http://www.cloudfour.com/we-have-disabled-wp-super-cache/comment-page-1/#comment-5135</link>
		<dc:creator>Thomas</dc:creator>
		<pubDate>Sun, 17 May 2009 18:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.cloudfour.com/?p=253#comment-5135</guid>
		<description>What about disabling the cache just for mobile users? That would reduce the hit on regular users, and allow adoption for mobile users as well.
I used the following approach: I added the iPhone User-Agent as being uncached (both in htaccess and WPSC). It works like a charm, with the tradeoff that mobile users are not served from the cache. But better than no (super) cache at all.
For example add this line after the HTTP_COOKIE line in .htaccess
RewriteCond %{HTTP_USER_AGENT} !^.+iPhone</description>
		<content:encoded><![CDATA[<p>What about disabling the cache just for mobile users? That would reduce the hit on regular users, and allow adoption for mobile users as well.<br />
I used the following approach: I added the iPhone User-Agent as being uncached (both in htaccess and WPSC). It works like a charm, with the tradeoff that mobile users are not served from the cache. But better than no (super) cache at all.<br />
For example add this line after the HTTP_COOKIE line in .htaccess<br />
RewriteCond %{HTTP_USER_AGENT} !^.+iPhone</p>
]]></content:encoded>
	</item>
</channel>
</rss>
