<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 24 May 2013 08:59:42 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Bas de Nooijer's Blog: Controlling Varnish ESI inside your application]]></title>
      <guid>http://www.phpdeveloper.org/news/14802</guid>
      <link>http://www.phpdeveloper.org/news/14802</link>
      <description><![CDATA[<p>
As is <a href="http://devzone.zend.com/article/12319-Varnish-Edge-Side-Includes">mentioned</a> on the Zend Developer Zone, there's a new post from <i>Bas de Nooijer</i> about a cool feature of <a href="http://varnish-cache.org/">Varnish</a> - Edge Side Includes - and <a href="http://blog.raspberry.nl/2010/07/05/controlling-varnish-esi-inside-your-application/">how you can control them</a>.
</p>
<blockquote>
For me one of the best features of Varnish is ESI (Edge Side Includes).  It allows you to combine elements with different lifetimes into a single page. This way you don't need to regenerate a complete page as soon as a news listing somewhere on the page changes. And you can still cache pages while displaying user-specific information somewhere on the page. This lowers the load on your application even further and it can also help in simplifying your application, by focussing purely on the content of the page and loading all other elements via ESI.
</blockquote>
<p>
He talks about the upsides and downsides to using the technique and what to avoid when implementing it in your Varnish config. One solution to the problem is sending an ESI "marker" to tell Varnish that a certain bit of content needs to be updated. He shows how to put it to use with a Zend Framework view helper that adds a special "esi" tag to the page when the content for a URL needs to be updated.
</p>]]></description>
      <pubDate>Fri, 16 Jul 2010 08:50:57 -0500</pubDate>
    </item>
  </channel>
</rss>
