<?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>Thu, 15 May 2008 22:34:48 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Larry Garfield's Blog: Drupal 7 gets introspective code registry]]></title>
      <guid>http://www.phpdeveloper.org/news/10143</guid>
      <link>http://www.phpdeveloper.org/news/10143</link>
      <description><![CDATA[<p>
<i>Larry Garfield</i> talks about a new feature of Drupal 7 in <a href="http://www.garfieldtech.com/drupal-7-registry">a new post</a> to his blog - the new introspective code registry that's been introduced in this latest version.
</p>
<blockquote>
As a GHOP Task , Cornil did a performance analysis of Drupal and found its two largest performance drains were the bootstrap process and the theming layer. Quite simply, Drupal spends too much time including code. [...] Fortunately, Drupal 7's self-learning <a href="http://drupal.org/node/221964">code registry system</a> has <a href="http://drupal.org/cvs?commit=114916">just</a> <a href="http://drupal.org/cvs?commit=114932">landed</a>, which should obliterate most of the wasted bootstrap cost.
</blockquote>
<p>
<i>Larry</i> <a href="http://www.garfieldtech.com/drupal-7-registry">describes</a> the "heart of it all", the token_get_all call, that parses through an entire PHP file, splitting out things like classes included and functions called. This is passed through a function_exists call to the current script and, if it's already there, the file isn't included repetitively.
</p>]]></description>
      <pubDate>Thu, 08 May 2008 12:53:14 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Alan Knowles' Blog: Another 7 deadly sins for PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/9853</guid>
      <link>http://www.phpdeveloper.org/news/9853</link>
      <description><![CDATA[<p>
In some thoughts related to the just-passed religious holiday, <i>Alan Knowles</i> decided to come up with another series of <a href="http://www.akbkhome.com/blog.php/View/160/Another_7_deadly_sins_for_PHP.html">7 deadly sins</a> one could commit in their PHP (CMS) development.
</p>
<p>Among those on the list are things like:</p>
<ul>
<li>Defines for configuration
<li>Filenaming
<li>If your code is public, you should try not to ridicule yourself.
<li>Mixing PHP and HTML
</ul>
<p>
Check out the <a href="http://www.akbkhome.com/blog.php/View/160/Another_7_deadly_sins_for_PHP.html">rest of the post</a> and some of the interesting comments that follow.
</p>]]></description>
      <pubDate>Tue, 25 Mar 2008 11:19:29 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Developer Tutorials Blog: And the winner of the most important security tip competition is...]]></title>
      <guid>http://www.phpdeveloper.org/news/9642</guid>
      <link>http://www.phpdeveloper.org/news/9642</link>
      <description><![CDATA[<p>
The Developer Tutorials blog has posted <a href="http://www.developertutorials.com/blog/php/most-important-php-security-tip-34/">their "winner"</a> of a list of things to do to keep you and your website secure:
</p>
<blockquote>
When it comes to PHP security, you often think of input filtering, SQL injection prevention, XSS in user submitted content and so on. Well, forget about that. They're all pretty trivial compared to what I feel is by far the most important security issue of any web application. Read on to find out why.
</blockquote>
<p>
Their number one thing to do to keep safe and secure? "Keep your systems updated." They point out that security a web site is one thing but securing the system that it runs on/has been developed on is another (and improperly patched, it could cause some huge problems). 
</p>
<blockquote>
Now, the best way to keep on top of potential vulnerabilities in your underlying systems is with updates. Sometimes, however, you need to go a little further. [...] Watching the web is also a good idea; major security vulnerabilities generally make it to the front page of Digg.
</blockquote>]]></description>
      <pubDate>Fri, 15 Feb 2008 09:31:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[DeveloperTutorials.com: Simple System Maintenance with PHP-CLI]]></title>
      <guid>http://www.phpdeveloper.org/news/9455</guid>
      <link>http://www.phpdeveloper.org/news/9455</link>
      <description><![CDATA[<p>
On the Developer Tutorials site today, there's <a href="http://www.developertutorials.com/tutorials/php/simple-system-maintenance-with-php-cli-8-01-17/page1.html">a new tutorial</a> posted that walks you through some of the useful features that PHP's CLI functionality can bring to your system administration.
</p>
<blockquote>
In this tutorial, I'll show you how to use PHP-CLI, the command line interface for PHP, to get your maintenance under control using the technologies you're already familiar with. I'll also examine some of the By the time you've finished this tutorial, you'll be able to build human-assisted backup systems, automatic report generators.
</blockquote>
<p>
It's a pretty <a href="http://www.developertutorials.com/tutorials/php/simple-system-maintenance-with-php-cli-8-01-17/page1.html">basic introduction</a> that talks about what the CLI environment is and what sorts of things PHP brings to the table. They include some sample scripts to do things like database cleanup and a method for taking in human interaction via the command line.
</p>]]></description>
      <pubDate>Mon, 21 Jan 2008 07:58:00 -0600</pubDate>
    </item>
  </channel>
</rss>
