<?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, 04 Jul 2008 21:59:00 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Tiger Heron Blog: First steps with PHP - booting a script, Part 2]]></title>
      <guid>http://www.phpdeveloper.org/news/10056</guid>
      <link>http://www.phpdeveloper.org/news/10056</link>
      <description><![CDATA[<p>
<i>Tony Freixas</i> continues his introductory look at "booting" a PHP script with <a href="http://www.tigerheron.com/article/2008/04/first-steps-php-booting-script-part-2">part two</a> of his series (here's <a href="http://www.phpdeveloper.org/news/9819">part one</a>) looking at using libraries.
</p>
<blockquote>
In the good old days, if you wanted to create re-usable code, you would create a library of related functions or objects. Now, the excitement is all around frameworks. Everyone has one. What is the difference between the two?
</blockquote>
<p>
He compares a library and a framework, pointing out key differences like how they fit with the application (controlled by or controlling) and dependencies they require. He rounds out his boot sequence, adding a few new parts to the structure of his example application.
</p>]]></description>
      <pubDate>Mon, 28 Apr 2008 12:57:33 -0500</pubDate>
    </item>
  </channel>
</rss>
