<?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>Mon, 12 May 2008 17:29:00 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[IBM developerWorks: Five more PHP design patterns]]></title>
      <guid>http://www.phpdeveloper.org/news/9875</guid>
      <link>http://www.phpdeveloper.org/news/9875</link>
      <description><![CDATA[<p>
The IBM developerWorks site has a <a href="http://www.ibm.com/developerworks/opensource/library/os-php-designpatterns/index.html?ca=drs-tp1308">new article</a> posted that talks about design patterns, five of them in particular, that can help to "accelerate your PHP development" and make your code more maintainable down the line.
</p>
<blockquote>
As an application developer, you can have a lifelong career without ever knowing what any of the patterns are called or how or when they're used. However, I've found that a good working knowledge of these patterns, as well as those introduced in the developerWorks article "Five common PHP design patterns" (see <a href="http://www.ibm.com/developerworks/opensource/library/os-php-designpatterns/index.html?ca=drs-tp1308#resources">Resources</a>), allows you to do two things: Enable high-bandwidth conversations and reduce painful lessons.
</blockquote>
<p>
The patterns they talk about in this "five more" article of the series are:
</p>
<ul>
<li>Adapter Pattern
<li>Iterator Pattern
<li>Decorator Pattern
<li>Delegate Pattern
<li>State Pattern
</ul>
<p>
Diagrams are provided for each of them, showing how they flow along with brief code examples (structures really) to show how that transitions over to actual use.
</p>]]></description>
      <pubDate>Fri, 28 Mar 2008 08:49:35 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[OReilly: Managing Sessions and State with PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/5401</guid>
      <link>http://www.phpdeveloper.org/news/5401</link>
      <description><![CDATA[<p>
In <a href="http://www.onlamp.com/pub/a/php/2006/05/18/managing-sessions-and-state.html?CMP=OTC-6YE827253101&ATT=Managing+Sessions+and+State+with+PHP">this new article</a> from the PHP DevCenter on the O'Reilly site today, they provide an introduction to a concept that PHP developers just starting out will definitely need for their future applications - sessions and state management.
</p>
<quote>
<i>
<p>
MVC Frameworks, such as <a href="http://wasp.sourceforge.net/">WASP</a>, provide a solid jumping-off point for entry-level programmers to produce strong, well-formed code. The framework simplifies such things as creating a page (using a kind of page object) and creating or searching for data (using database table objects).
</p>
<p>
However, probably the most difficult concept for novice PHP programmers to grasp is handling their application's state and session data. This article will address that issue by providing a simple strategy for state management using the WASP framework.
</p>
</i>
</quote>
<p>
They <a href="http://www.onlamp.com/pub/a/php/2006/05/18/managing-sessions-and-state.html?CMP=OTC-6YE827253101&ATT=Managing+Sessions+and+State+with+PHP">start</a. with the difference between session state and page state, and include examples for each. Both examples include code to illustrate the point and some explaination for it each step of the way. All of the sample code is written within the WASP framework, so if you're unfamiliar, you might want to check out their <a href="http://www.phpdeveloper.org/news/4699">previous article</a> for an introduction.
</p>]]></description>
      <pubDate>Fri, 19 May 2006 06:18:25 -0500</pubDate>
    </item>
  </channel>
</rss>
