<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Random Musings of an Insane Mind &#187; esi</title>
	<atom:link href="http://cd34.com/blog/tag/esi/feed/" rel="self" type="application/rss+xml" />
	<link>http://cd34.com/blog</link>
	<description>This is my blog, there are many others like it but this one is mine.</description>
	<lastBuildDate>Thu, 02 Feb 2012 20:47:03 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Finally, a formal release for my WordPress + Varnish + ESI plugin</title>
		<link>http://cd34.com/blog/infrastructure/finally-a-formal-release-for-my-wordpress-varnish-esi-plugin/</link>
		<comments>http://cd34.com/blog/infrastructure/finally-a-formal-release-for-my-wordpress-varnish-esi-plugin/#comments</comments>
		<pubDate>Tue, 10 Jan 2012 09:06:40 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Web Infrastructure]]></category>
		<category><![CDATA[esi]]></category>
		<category><![CDATA[Varnish]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=1329</guid>
		<description><![CDATA[A while back I wrote a plugin to take care of a particular client traffic problem. As the traffic came in very quickly and unexpectedly, I had only minutes to come up with a solution. As I knew Varnish pretty well, my initial reaction was to put the site behind Varnish. But, there&#8217;s a problem [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/infrastructure/finally-a-formal-release-for-my-wordpress-varnish-esi-plugin/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>When to Cache, What to Cache, How to Cache</title>
		<link>http://cd34.com/blog/infrastructure/when-to-cache-what-to-cache-how-to-cache/</link>
		<comments>http://cd34.com/blog/infrastructure/when-to-cache-what-to-cache-how-to-cache/#comments</comments>
		<pubDate>Tue, 21 Jun 2011 22:17:15 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Web Infrastructure]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[cdn]]></category>
		<category><![CDATA[esi]]></category>
		<category><![CDATA[Varnish]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=929</guid>
		<description><![CDATA[This post is a version of the slideshow presentation I did at Hack and Tell in Fort Lauderdale, Florida at The Collide Factory on Saturday, April 2, 2011. These are 5 minute talks where each slide auto-advances after fifteen seconds which limits the amount of detail that can be conveyed. A brief introduction What makes [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/infrastructure/when-to-cache-what-to-cache-how-to-cache/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>WordPress, Varnish and ESI Plugin</title>
		<link>http://cd34.com/blog/scalability/wordpress-varnish-and-esi-plugin/</link>
		<comments>http://cd34.com/blog/scalability/wordpress-varnish-and-esi-plugin/#comments</comments>
		<pubDate>Mon, 06 Jun 2011 02:28:16 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Scalability]]></category>
		<category><![CDATA[esi]]></category>
		<category><![CDATA[Varnish]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=1177</guid>
		<description><![CDATA[This post is a version of the slideshow presentation I did at Hack and Tell in Fort Lauderdale, Florida at The Whitetable Foundation on Saturday, June 4, 2011. Briefly, I created a Plugin that enabled Fragment Caching with WordPress and Varnish. The problem we ran into with normal page caching methods was related to the [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/scalability/wordpress-varnish-and-esi-plugin/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>WordPress Varnish ESI Widget is back.  Thank you Varnish.</title>
		<link>http://cd34.com/blog/infrastructure/wordpress-varnish-esi-widget-is-back-thank-you-varnish/</link>
		<comments>http://cd34.com/blog/infrastructure/wordpress-varnish-esi-widget-is-back-thank-you-varnish/#comments</comments>
		<pubDate>Wed, 26 Jan 2011 14:15:37 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Web Infrastructure]]></category>
		<category><![CDATA[esi]]></category>
		<category><![CDATA[Varnish]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=1117</guid>
		<description><![CDATA[Long ago I wrote the WordPress ESI Widget to help a client&#8217;s site stay online during a barrage of traffic. To solve some of the performance problems on high traffic WordPress sites, you have to use caching, but almost all of the caching addons for WordPress do page level caching rather than fragment caching. After [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/infrastructure/wordpress-varnish-esi-widget-is-back-thank-you-varnish/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Django CMS to support Varnish and Akamai ESI</title>
		<link>http://cd34.com/blog/framework/django-cms-to-support-varnish-and-akamai-esi/</link>
		<comments>http://cd34.com/blog/framework/django-cms-to-support-varnish-and-akamai-esi/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 22:50:00 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Framework]]></category>
		<category><![CDATA[akamai]]></category>
		<category><![CDATA[cms]]></category>
		<category><![CDATA[django]]></category>
		<category><![CDATA[esi]]></category>
		<category><![CDATA[pylons]]></category>
		<category><![CDATA[Varnish]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=870</guid>
		<description><![CDATA[Many years ago I ran into a situation with a client where the amount of traffic they were receiving was crushing their dynamically created site. Computation is always the enemy of a quick pageload, so, it is very important to do as little computation as possible when delivering a page. While there are many ways [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/framework/django-cms-to-support-varnish-and-akamai-esi/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>No ESI processing, first char not &#8216;</title>
		<link>http://cd34.com/blog/infrastructure/no-esi-processing-first-char-not/</link>
		<comments>http://cd34.com/blog/infrastructure/no-esi-processing-first-char-not/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 03:26:49 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Web Infrastructure]]></category>
		<category><![CDATA[edge side include]]></category>
		<category><![CDATA[esi]]></category>
		<category><![CDATA[Varnish]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=837</guid>
		<description><![CDATA[After installing Varnish 2.0.5 on a machine, ESI Includes didn&#8217;t work. When using varnishlog, the first error that occurred when debugging was: No ESI processing, first char not &#8216;< ' 12 SessionClose &#8211; timeout 12 StatSess &#8211; 124.177.181.149 50662 4 0 0 0 0 0 0 0 12 SessionOpen c 68.212.183.136 60087 66.244.147.44:80 12 ReqStart [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/infrastructure/no-esi-processing-first-char-not/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ESI Widget Issues in the Varnish, ESI, WordPress experiment</title>
		<link>http://cd34.com/blog/scalability/esi-widget-issues-in-the-varnish-esi-wordpress-experiment/</link>
		<comments>http://cd34.com/blog/scalability/esi-widget-issues-in-the-varnish-esi-wordpress-experiment/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 01:41:16 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Scalability]]></category>
		<category><![CDATA[esi]]></category>
		<category><![CDATA[Varnish]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=729</guid>
		<description><![CDATA[The administration interface is quite simple. When the widget is installed, drag it to the Sidebar, then, drag any widgets that you want displayed to the ESI Widget Sidebar. Current issues: * When a user is logged in and comments on a post, their &#8216;login&#8217; information is left on the page if they are the [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/scalability/esi-widget-issues-in-the-varnish-esi-wordpress-experiment/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>WordPress, Varnish and Edge Side Includes</title>
		<link>http://cd34.com/blog/scalability/wordpress-varnish-and-edge-side-includes/</link>
		<comments>http://cd34.com/blog/scalability/wordpress-varnish-and-edge-side-includes/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 19:34:29 +0000</pubDate>
		<dc:creator>cd34</dc:creator>
				<category><![CDATA[Scalability]]></category>
		<category><![CDATA[esi]]></category>
		<category><![CDATA[Varnish]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://cd34.com/blog/?p=723</guid>
		<description><![CDATA[While talking about WordPress and it&#8217;s abysmal performance in high traffic situations to a client, we started looking back at Varnish and other solutions to keep their machine responsive. Since most of the caching solutions generate a page, serve it and cache it, posts and comments tend to lag behind the cache. db-cache does work [...]]]></description>
		<wfw:commentRss>http://cd34.com/blog/scalability/wordpress-varnish-and-edge-side-includes/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>

