<?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, 09 Jul 2008 07:13:52 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[DevShed: Using Timers to Benchmark PHP Applications]]></title>
      <guid>http://www.phpdeveloper.org/news/10082</guid>
      <link>http://www.phpdeveloper.org/news/10082</link>
      <description><![CDATA[<p>
DevShed has posted the <a href="http://www.devshed.com/c/a/PHP/Using-Timers-to-Benchmark-PHP-Applications/">second article</a> in their series looking at benchmarking your PHP scripts. This time they look at the use of "timers" to check on script execution length.
</p>
<blockquote>
Since you already know how to create timer functions and classes, in this tutorial, I'll create some concrete examples that show where these timing mechanisms can be applied in order to evaluate the performance of certain PHP applications.
</blockquote>
<p>
They <a href="http://www.devshed.com/c/a/PHP/Using-Timers-to-Benchmark-PHP-Applications/1/">create a few classes</a> that connect to a database and pull out rows (handing it off to a Result class). They use these classes in two examples - one with compression (output buffering) and one without using their Timer class to evaluate the differences.
</p>]]></description>
      <pubDate>Wed, 30 Apr 2008 14:31:08 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[PHPit.net: Having fun with PHP's output buffer]]></title>
      <guid>http://www.phpdeveloper.org/news/5186</guid>
      <link>http://www.phpdeveloper.org/news/5186</link>
      <description><![CDATA[<p>
One of the more powerful and handy features that PHP offers is output buffering. It allows you more control over when the client's browser gets the information instead of just spewing information at random. It is a little tricky to get the hang of, so PHPit.net has put together <a href="http://www.phpit.net/article/output-buffer-fun-php/">this new tutorial</a> on how to get started.
</p>
<quote>
<i>
<p>
I'm sure most of us have come across the dreaded "Cannot modify header information - headers already sent", and this is usually caused when your script tries to send a header or set a cookie, when it's already sent output. The easiest fix is to make sure no output has been sent, but it's also possible to enable something called output buffering which also solves the problem.
</p>
<p>
In this article I'll first show you how output buffering works, and take you through most of its basic functions. After that we'll have a look at what's possible with output buffering, and show you some neat tricks.
</p>
</i>
</quote>
<p>
The <a href="http://www.phpit.net/article/output-buffer-fun-php/">groundwork</a> is laid first, giving a simple "Hello world" example to show how the code flows. They show how the buffering system works and how to use a callback function to modify the contents of the buffer before outputting (including a full replace function to text within the buffer from an array). They follow that with a look at creating your own HTML tags and using the gzip compression functionality to speed up your pages. 
</p>]]></description>
      <pubDate>Mon, 17 Apr 2006 07:13:24 -0500</pubDate>
    </item>
  </channel>
</rss>
