<?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, 19 May 2013 03:52:36 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Padraic Brady's Blog: The M in MVC: Why Models are Misunderstood and Unappreciated]]></title>
      <guid>http://www.phpdeveloper.org/news/11505</guid>
      <link>http://www.phpdeveloper.org/news/11505</link>
      <description><![CDATA[<p>
In <a href="http://blog.astrumfutura.com/archives/373-The-M-in-MVC-Why-Models-are-Misunderstood-and-Unappreciated.html">this new post</a> to his blog <i>Padraic Brady</i> looks at why models are "misunderstood and unappreciated" in a Model/View/Controller sort of world.
</p>
<blockquote>
By the time I'd finished both chapters [of my Zend Framework book] I realised I had spent a lot of space explaining the Model, most of it discussing how the Zend Framework does not actually give you one. In fact, no web application framework offers a complete Model (for reasons I'll explain later). However nearly all frameworks manage to avoid making that perfectly obvious. Instead they continually link the concept of a Model to the related, but not identical, concept of data access. This is quite misleading.
</blockquote>
<p>
He looks at two things models are good for (maintaining state and enforcing rules on the data in the current state), how it seems most PHP developers perceive them, how controllers can be turned into "mutated models" and the idea that models should be classes and controllers are just processes (handlers for requests).
</p>]]></description>
      <pubDate>Thu, 04 Dec 2008 11:19:36 -0600</pubDate>
    </item>
  </channel>
</rss>
