<?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 15:48:49 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[phpaddiction: Url Routing with PHP - Part One]]></title>
      <guid>http://www.phpdeveloper.org/news/7532</guid>
      <link>http://www.phpdeveloper.org/news/7532</link>
      <description><![CDATA[<p>
The phpaddiction website has posted <a href="http://www.phpaddiction.com/tags/axial/url-routing-with-php-part-one/">the first part of a series</a> today covering URL routing with PHP (commonly used by frameworks to route requests through a centralized location.
</p>
<blockquote>
Most PHP frameworks use some variation of the front controller pattern to centralize common code and logic. There are advantages and disadvantages to this. I am going to ignore those for now. In fact the first part of this series will explore a simple procedural URL routing method that contains many of the disadvantages. In later articles we will build upon this basis and address the disadvantages.
</blockquote>
<p>
He walks through <a href="http://www.phpaddiction.com/tags/axial/url-routing-with-php-part-one/">the steps</a> to get things set up - working with mod_rewrite, creating the "entry point" for your application, and finally, how to execute a command based on the request's action.
</p>]]></description>
      <pubDate>Fri, 30 Mar 2007 08:12:00 -0500</pubDate>
    </item>
  </channel>
</rss>
