<?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>Sat, 18 May 2013 18:16:16 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Zend Developer Zone: Chris Hartjes on Learning From Ruby on Rails]]></title>
      <guid>http://www.phpdeveloper.org/news/6799</guid>
      <link>http://www.phpdeveloper.org/news/6799</link>
      <description><![CDATA[<p>
In <a href="http://devzone.zend.com/node/view/id/1281">this post</a> on the Zend Developer Zone, <i>Cal Evans</i> takes a look at an article published in a recent <a href="http://www.phparchitect.com/">php|architect</a> issue from <i>Chris Hartjes</i> about how several recent advancements in the PHP community have helped developers think more in "the Rails way" of development.
</p>
<blockquote>
Chris does a good job of laying out his points. As with any article of this nature, you are going to agree with some of them and you'll disagree with some of them. However, to get to that point you'll have to consider all of them. That's really the point of the article; making developer sit back and think for a minute. It's well worth the read.
</blockquote>
<p>
<i>Cal</i> <a href="http://devzone.zend.com/node/view/id/1281">also mentions</a> some of the topics presented in the article including more conceptual ideas like "Convention Over Configuration" and "Rapid Should Mean Rapid".
</p>]]></description>
      <pubDate>Thu, 30 Nov 2006 10:29:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Alexander Netkachev's Blog: Practical PHP events: The Java way]]></title>
      <guid>http://www.phpdeveloper.org/news/6625</guid>
      <link>http://www.phpdeveloper.org/news/6625</link>
      <description><![CDATA[<p>
Continuing on with his look at events in PHP, <i>Alexander Netkachev</i> takes <a href="http://www.alexatnet.com/Blog/Index/2006-10-31/practical-php-events-the-java-way">another look today</a> at another type of approach to his handy feature - the "Java way".
</p>
<blockquote>
In my previous article I summarized event system definitions and showed an example of PHP event model, which is built with the call_user_func() function. This acticle expands the subject by introducing an advanced PHP event model that is based on sender/eventObject/listener collaboration, which was popularized by the Java world.
</blockquote>
<p>
He <a href="http://www.alexatnet.com/Blog/Index/2006-10-31/practical-php-events-the-java-way">steps through</a> some examples with ProtocolCommandSupport.java and ProtocolCommandListener.java functionality, showing how to take that functionality back over to PHP and implement it using the built-in features.
</p>]]></description>
      <pubDate>Wed, 01 Nov 2006 13:58:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Paul Jones' Blog: ASP-Style Programming in PHP?]]></title>
      <guid>http://www.phpdeveloper.org/news/5243</guid>
      <link>http://www.phpdeveloper.org/news/5243</link>
      <description><![CDATA[<p>
In a <a href="http://paul-m-jones.com/blog/?p=207">new post</a> on his blog today, <i>Paul Jones</i> mentions a framework that might bridge the gap for ASP developers making the move over to PHP, <a href="http://www.pradosoft.com/">Prado</a>, and some of the issues that more traditional PHP developers might see around it.
</p>
<quote>
<i>
<p>
An old buddy of mine wants to start using PHP, but the problem is that he's been working with Microsoft technologies for so long, he doesn't get "the PHP way". His background, for many years, has been with ASP.NET, COM, and those sorts of things.
</p>
<p>
As it turns out, there's a PHP framework out there that maps well to "the ASP.NET way": Prado.
</p>
</i>
</quote>
<p>
He talks about <a href="http://paul-m-jones.com/blog/?p=207">how the framework is structured</a> and what non-PHPers might find to like about it, but he also wonders if the phrase "the PHP way" might be better replaced by a more definitive term to describe the way most PHP develoers prefer their apps to work.
</p>]]></description>
      <pubDate>Wed, 26 Apr 2006 16:12:56 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Greg Beaver's Blog: Setting up your own PEAR channel - the official way]]></title>
      <guid>http://www.phpdeveloper.org/news/5072</guid>
      <link>http://www.phpdeveloper.org/news/5072</link>
      <description><![CDATA[In conjection with the release of PEAR 1.4.9 as <a href="http://www.phpdeveloper.org/news/5069">previously mentioned</a>, <i>Greg Beaver</i> wants to clarify some things when it comes to setting up a PEAR channel in "the official way" and with the correct pakcages.
<p>
There has been quite a bit of confusion recently due to the best resource for setting up a channel being located on <a href="http://schlitt.info/applications/blog/index.php/archives/308-Set-up-your-own-PEAR-channel.html">Toby's blog</a>, and now being quite a few versions out of date. First of all, let it be known that the <a href="http://pear.chiaraquartet.net/index.php?package=PEAR_Server">PEAR_Server</a> package located at pear.chiaraquartet.net has been superseded by the <a href="http://pear.chiaraquartet.net/index.php?package=Chiara_PEAR_Server">Chiara_PEAR_Server</a> package at pear.chiaraquartet.net.
</i>
</quote>
<p>
The rest of <a href="http://greg.chiaraquartet.net/archives/123-Setting-up-your-own-PEAR-channel-the-official-way.html">the post</a> is concerned with his checklist and step-by-step guide to getting and setting up the needed software. It's the whole process, right down to creating a nice frontend for the users and how to test your channel to ensure it's properly set up. 
<p>
It's definitely the <a href="http://greg.chiaraquartet.net/archives/123-Setting-up-your-own-PEAR-channel-the-official-way.html">definitive guide</a> to setting up a PEAR channel correctly.]]></description>
      <pubDate>Thu, 30 Mar 2006 07:27:49 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Builder.com.au: LAMP lights way on open source security]]></title>
      <guid>http://www.phpdeveloper.org/news/4947</guid>
      <link>http://www.phpdeveloper.org/news/4947</link>
      <description><![CDATA[From Builder.co.au, there's <a href="http://www.builderau.com.au/program/work/soa/LAMP_lights_way_on_open_source_security/0,39024650,39237780,00.htm?feed=rss">this new article</a> that talks about the LAMP software, how's it's "showing the way" to Open Source security.
<p>
<quote>
<i>
The most popular open-source software is also the most free of bugs, according to the first results of a U.S. government-sponsored effort to help make such software as secure as possible.
<p>
The so-called LAMP stack of open-source software has a lower bug density--the number of bugs per thousand lines of code--than a baseline of 32 open-source projects analysed, Coverity, a maker of code analysis tools, announced Monday.
</i>
</quote>
<p>
<a href="http://www.builderau.com.au/program/work/soa/LAMP_lights_way_on_open_source_security/0,39024650,39237780,00.htm?feed=rss">The results</a> are a product of a Homeland Security effort (performed by Stanford University) for three years. They found that the LAMP combination contained about 0.434 bugs per 1,000 lines of code. Unfortunately, their results also showed, of those problems, PHP had the higest bug count of the four.]]></description>
      <pubDate>Tue, 07 Mar 2006 07:25:42 -0600</pubDate>
    </item>
  </channel>
</rss>
