<?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>Tue, 21 May 2013 22:41:06 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[DevShed: Introducing the Facade Pattern in PHP 5]]></title>
      <guid>http://www.phpdeveloper.org/news/7101</guid>
      <link>http://www.phpdeveloper.org/news/7101</link>
      <description><![CDATA[<p>
DevShed continues with their look at design patterns in PHP with <a href="http://www.devshed.com/c/a/PHP/Introducing-the-Facade-Pattern-in-PHP-5/">the first part</a> of a new series today discussing the Facade pattern as created in PHP 5.
</p>
<blockquote>
In this case, you have a class that hides all the complexity required for serializing the mentioned objects, but there's also a group of classes that know nothing about the class that called them. As you can see, these classes are only responsible for performing the serialization/unserialization sequence on several objects and nothing else. Period.
</blockquote>
<p>
The Facade pattern is best seen as an interface between the real meat of the application and the part that displays the results. It provides a buffer between the two to make it easier for the output class to call. They create a <a href="http://www.devshed.com/c/a/PHP/Introducing-the-Facade-Pattern-in-PHP-5/2/">basic implementation</a> of this and show how to use compression and provide all the code you'll need to get it working.
</p>]]></description>
      <pubDate>Tue, 16 Jan 2007 11:19:00 -0600</pubDate>
    </item>
  </channel>
</rss>
