<?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, 07 Sep 2008 10:00:38 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[The Show (CakePHP Podcast): Understanding FormHelper]]></title>
      <guid>http://www.phpdeveloper.org/news/8766</guid>
      <link>http://www.phpdeveloper.org/news/8766</link>
      <description><![CDATA[<p>
The CakePHP podcast, "The Show" has <a href="http://live.cakephp.org/shows/view/4">posted it's latest episode</a> - a spotlight on the FormHelper component of the framework:
</p>
<blockquote>
Nate Abele and Larry Masters join me to discuss the new FormHelper feature in CakePHP 1.2. This time we manage to stay on topic and sober. Join us for an archived hour of form developing goodness.
</blockquote>
<p>
You can either subscribe to their <a href="http://live.cakephp.org/shows/index.rss">normal feed</a>, their <a href="itpc://live.cakephp.org/shows/index.rss">iTunes feed</a> or you can just grab the show <a href="http://live.cakephp.org/shows/view/4.mp3">directly from the site</a> to enjoy the episode.
</p>]]></description>
      <pubDate>Tue, 02 Oct 2007 12:09:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[The Codist Blog: Followup To: I Will Never Understand the Appeal Of PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/6893</guid>
      <link>http://www.phpdeveloper.org/news/6893</link>
      <description><![CDATA[<p>
A few days back there was <a href="http://www.phpdeveloper.org/news/6873">a post</a> on the "The Codist" blog about why the author would never quite understand the appeal of PHP to the masses and some of his thoughts behind it. Well, there was such an outcry and response to his comments that he's written up <a href="http://codist.biit.com/fiche/thecodist/article/followup-to-i-will-never-understand-the-appeal-of-php">another post</a> on what he learned from comments made.
</p>
<blockquote>
Clearly I touched a nerve. However I did learn a lot of things that you don't read in a quickly tutorial on PHP. The whole point of writing something is to get feedback, positive or negative, and hopefully learn from it.
</blockquote>
<p>
He <a href="http://codist.biit.com/fiche/thecodist/article/followup-to-i-will-never-understand-the-appeal-of-php">admits</a> that his experience with PHP and its developers has been limited, so his perspective might have been thrown off a bit. He still holds to one thing from the previous article, though - that PHP just isn't for him.
</p>]]></description>
      <pubDate>Thu, 14 Dec 2006 07:11:32 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Tectonic.co.za: Getting your head around PHP objects]]></title>
      <guid>http://www.phpdeveloper.org/news/5976</guid>
      <link>http://www.phpdeveloper.org/news/5976</link>
      <description><![CDATA[<p>
In a new article from Tectonic today, <i>Jason Norwood-Young</i> <a href="http://www.tectonic.co.za/view.php?id=1094">takes a look at</a> one of the harder things for beginning PHP developers to understand - objects.
</p>
<blockquote>
<p>
Still the practice of using objects in PHP remains a bit of a lost art - you're more likely to find an application with a bunch of functions than objects. PHP just lends itself to function-like thinking.
</p>
<p>
That doesn't mean that you shouldn't take advantage of the object-oriented (OO) features of PHP. The big question is when. Deciding when to implement a bit of code as an object or as a function is the real trick of object-oriented programming (OOP) in PHP (or as I like to call it, POOP). If you get that right, you can save yourself a lot of time and hassle down the line.
</p>
</blockquote>
<p>
<i>Jason</i> <a href="http://www.tectonic.co.za/view.php?id=1094">starts off with the differences</a> between OOP and regular, procedural programming, explaining it with a series of reasons/times to choose OOP. Of course, code examples are a must, and a few are included, showing the structure of classes and how to create new objects from them. He explains the PHP5 functionality offered as well, including private/public/protected values and functions.
</p>]]></description>
      <pubDate>Tue, 08 Aug 2006 06:02:20 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Drupal.org: Tuning your server for optimal Drupal performance]]></title>
      <guid>http://www.phpdeveloper.org/news/5204</guid>
      <link>http://www.phpdeveloper.org/news/5204</link>
      <description><![CDATA[<p>
On the Drupal site, there's a <a href="http://drupal.org/node/2601">handy article</a> instructing you on getting the most performance out of your server for the <a href="http://drupal.org/">Drupal</a> software.
</p>
<quote>
<i>
The performance of your Drupal site is dependent on three main factors: the goals of your site, the resource demands of your site traffic, and the system performance and configuration of underlying technologies.
</i>
</quote>
<p>
They <a href="http://drupal.org/node/2601">seperate it out</a> into three different sections - setting out your performance goals, analysing your site for current traffic/resource consumption, and the actual implementation of the performance settings. They give a few steps here to follow to check what your server is currently using and some links to other tips on tuning the various pieces of the puzzle.
</p>
<p>
One thing that they mention that's worth repeating to any and all web developers out there: "Apache is bandwidth limited, PHP is CPU limited, and MySQL is memory limited and disk I/O bound".
</p>]]></description>
      <pubDate>Wed, 19 Apr 2006 07:14:14 -0500</pubDate>
    </item>
  </channel>
</rss>
