<?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>Wed, 23 May 2012 10:43:07 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Debuggable Blog: How To Save Half A Second On Every CakePHP Request]]></title>
      <guid>http://www.phpdeveloper.org/news/12038</guid>
      <link>http://www.phpdeveloper.org/news/12038</link>
      <description><![CDATA[<p>
CakePHP users might want to <a href="http://debuggable.com/posts/how-to-save-half-a-second-on-every-request-of-your-cakephp-app:49a69610-8648-4d65-815d-754c4834cda3">listen to this suggestion</a> from <i>Tim Koschutzki</i> on the Debuggable blog - he wants to help you save a half second on each request.
</p>
<blockquote>
There are several ways to improve the performance of your CakePHP application. [...] Any performance improvement that does not effect how data is retrieved, stored and cached is welcome. If it affects your entire site and not only parts of it, it's all the better.
</blockquote>
<p>
The performance boost comes in the form of an update to CakePHP's reverse route lookup functionality. Normally a lookup would have to be parsed and resolved back to their original location. They figured a bit faster way around it though - breaking the reverse routing feature for the sake of speed. The code for the hack is <A href="http://debuggable.com/posts/how-to-save-half-a-second-on-every-request-of-your-cakephp-app:49a69610-8648-4d65-815d-754c4834cda3">included in the post</a>.
</p>]]></description>
      <pubDate>Fri, 27 Feb 2009 12:09:51 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Antony Dovgal's Blog: PHP test coverage exceeded 55%]]></title>
      <guid>http://www.phpdeveloper.org/news/10229</guid>
      <link>http://www.phpdeveloper.org/news/10229</link>
      <description><![CDATA[<p>
As <i>Antony Dovgal</i> <a href="http://daylessday.org/archives/25-PHP-test-coverage-exceeded-55%23.html">points out</a> in a new blog post today, the latest reports on PHP's <a href="http://gcov.php.net/PHP_5_3/lcov_html/">code coverage</a> have jumped up over the 50% mark (to 56.3% at the time of this post).
</p>
<blockquote>
It took us about 2 years to get the last 5% and I believe most of the kudos should go to IBM people, who continue to contribute lots of new tests. I hope that <a href="http://qa.php.net/testfest.php">the Testfest</a> will help us to speed up this process.
</blockquote>
<p>
There are still a lot of items <a href="http://gcov.php.net/PHP_5_3/lcov_html/">in the red</a> that could use some tests, so if you're looking to help out write up some tests or check your area for a <a href="http://qa.php.net/testfest.php">TestFest</a> event to get some help.
</p>]]></description>
      <pubDate>Wed, 21 May 2008 08:47:44 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Andrei Zmievski's Blog: 50% There]]></title>
      <guid>http://www.phpdeveloper.org/news/6945</guid>
      <link>http://www.phpdeveloper.org/news/6945</link>
      <description><![CDATA[<p>
<i>Andrei Zmievski</i> has posted an <a href="http://www.gravitonic.com/blog/archives/000305.html">encouraging note</a> on his blog about the progress of PHP6 concerning the number of functions that have been correctly converted to support Unicode.
</p>
<blockquote>
Well, PHP boys and girls, this feels like quite a milestone: 50% of the 3084 functions that are bundled with PHP 6 have been upgraded to support and work safely with Unicode.
</blockquote>
<p>
He <a href="http://www.gravitonic.com/blog/archives/000305.html">includes a small chart</a> beside the post as well showing where things are currently at like the safe vs unsafe functions.
</p>]]></description>
      <pubDate>Wed, 20 Dec 2006 08:08:02 -0600</pubDate>
    </item>
  </channel>
</rss>

