<?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>Fri, 09 Jan 2009 06:44:08 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[SitePoint PHP Blog: The sysadmin view on "Why PHP"]]></title>
      <guid>http://www.phpdeveloper.org/news/4650</guid>
      <link>http://www.phpdeveloper.org/news/4650</link>
      <description><![CDATA[On the SitePoint PHP Blog today, <i>Harry Fuecks</i> takes a look at <a href="http://www.sitepoint.com/blogs/2006/01/10/the-sysadmin-view-on-why-php/">why PHP</a> from a sysadmin's perspective. 
<p>
<quote>
<i>
A funny from the Python crowd: phpfilter'"PHP "support" under CherryPy. There is a serious side to that though'"it's spitting out something that looks like a PHP parse error'"i.e. this is a developer problem (e.g. someone ftp'd a PHP straight onto their live web server for 'testing'), not a runtime error.
<p>
More to the point, when was the last time you saw a PHP runtime error take down an entire application or web server? And no - "MySQL Connection Failed: Can't connect to local MySQL server" doesn't count'"PHP and the web server are still running'"the MySQL server (or otherwise) is to blame.
</i>
</quote>
<p>
He <a href="http://www.sitepoint.com/blogs/2006/01/10/the-sysadmin-view-on-why-php/">also looks</a> at a slightly different method for serving up web applications - with <a href="http://www.fastcgi.com/">FastCGI</a>. He talks about the basic features of a server (forking, threading, asynchronous I/O) and how that explains how we've ended up with PHP being the "lesser of the evils"...]]></description>
      <pubDate>Thu, 12 Jan 2006 06:42:35 -0600</pubDate>
    </item>
  </channel>
</rss>
