<?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>Sun, 19 May 2013 14:14:33 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Robert Basic's Blog: Zend Framework full page cache tips]]></title>
      <guid>http://www.phpdeveloper.org/news/17533</guid>
      <link>http://www.phpdeveloper.org/news/17533</link>
      <description><![CDATA[<p>
If you're looking at using the full-page caching that the Zend Framework has to offer, you should <a href="http://robertbasic.com/blog/zend-framework-full-page-cache-tips">read about Robert Basic's experiences</a> with it before implementing it in your application.
</p>
<blockquote>
When I started rewriting this blog, I knew from start that I want to use Zend Framework's full page caching, as, I think, that's the best cache for this purpose. Not much going on on the front end, much more reads than writes, no ajax or any other "dynamic" content. While implementing the cache, I ran into two issues.
</blockquote>
<p>
His issues revolved around the feature not creating valid cache files due to a duplicate "startSession" call in his code and having the Google Analytics code included in the template (with different keys every time). You can find out more about this functionality <a href="http://framework.zend.com/manual/en/zend.cache.frontends.html#zend.cache.frontends.page">in the Zend Framework manual</a>. 
</p>]]></description>
      <pubDate>Mon, 13 Feb 2012 11:45:10 -0600</pubDate>
    </item>
  </channel>
</rss>
