<?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>Sat, 25 May 2013 02:31:35 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Matthew Weier O'Phinney's Blog: Simple Interfaces and Micro MVCs]]></title>
      <guid>http://www.phpdeveloper.org/news/15624</guid>
      <link>http://www.phpdeveloper.org/news/15624</link>
      <description><![CDATA[<p>
In <a href="http://weierophinney.net/matthew/archives/250-Simple-Interfaces-and-Micro-MVCs.html">a new post</a> to his blog today <i>Matthew Weier O'Phinney</i> takes a look at micro MVC frameworks and how, with just a bit of lightweight code and pieces of the Zend Framework, creating one is dead simple.
</p>
<blockquote>
My job is great: I get to play with technology and code most days. My job is also hard: how does one balance both functionality and usability in programming interfaces? [...] One interface I've been toying with is inspired by two very different sources. The first is PHP's own <a href="http://php.net/SoapServer">SoapServer API</a> (which we use already in our various server components); the other was a discussion I had with <a href="http://fabien.potencier.org/">Fabien Potencier</a> (of Symfony fame) a couple years ago, where he said the goal of Symfony 2 would be "to transform a request into a response." 
</blockquote>
<p>
The result is a simple Dispatachable interface that acts as the lowest level to build the whole MVC on top of. He illustrates with a micro MVC example that uses the Dispatchable interface to create a Dispatcher class to handle the incoming requests and attach various endpoints for handling. An example of it in use is also included.
</p>]]></description>
      <pubDate>Thu, 23 Dec 2010 09:29:07 -0600</pubDate>
    </item>
  </channel>
</rss>
