<?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 19:57:10 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Cognify.com: Write Your Own Virtual Host Control Panel - Part 1]]></title>
      <guid>http://www.phpdeveloper.org/news/10714</guid>
      <link>http://www.phpdeveloper.org/news/10714</link>
      <description><![CDATA[<p>
<i>Mark Kimsal</i> has <a href="http://cognifty.com/main.content/write_your_own_virtual_host_control_panel_part_1.html">posted part one</a> of a new series he's working up on creating a virtual host control panel by pairing with PHP a few other technologies.
</p>
<blockquote>
I still come across a person now and then who does not appreciate the power that any server control panel gives you. [...] They reduce the margin of error that a human can bring to the table when editing files and performing commands "by hand".  If host control panels are so good, why would you want to write your own control panel when there are so many out there already? Well, the answer is, there aren't any open source ones. 
</blockquote>
<p>
He talks about <a href="http://cognifty.com/main.content/write_your_own_virtual_host_control_panel_part_1.html/p=2">starting out right</a> by defining the build and the technology to use and only then gets started coding. His application uses the <a href="http://cognifty.com">Cognify</a> framework, SQLite, Nanoweb and, of course, PHP. At the <a href="http://cognifty.com/main.content/write_your_own_virtual_host_control_panel_part_1.html/p=5">end</a> of this part of the series, you'll have the framework set up and a sample module in place to mess with.
</p>]]></description>
      <pubDate>Wed, 30 Jul 2008 09:31:13 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Mark Kimsal's Blog: Is Your MVC MIA When it Comes to 404s?]]></title>
      <guid>http://www.phpdeveloper.org/news/10558</guid>
      <link>http://www.phpdeveloper.org/news/10558</link>
      <description><![CDATA[<p>
In a new post to his blog, <i>Michael Kimsal</i> points out a post from his brother (<i>Mark</i>) that <a href="http://cognifty.com/index.php/blog.entry/id=8/is_your_mvc_mia_when_it_comes_to_404s.html">wonders if your framework</a> handles 404 errors the best/most useful way it can.
</p>
<blockquote>
This post is about the consistency of frameworks. Consistency is key to a low learning curve. [...] Yesterday, my brother asked me how he could capture 404 errors in Cognifty, as he was building an app that relied on dealing with random URL patterns. [...] After talking for a bit, we decided that handing off the request to a standard service (or controller) was the best way to handle this type of "error". He started searching to see if other frameworks had a consistent, or at least documented, way of dealing with missing controllers.
</blockquote>
<p>
In his research he found one framework - the Zend Framework - that handed them by default as an error and passed them off to that handler. <i>Mark</i> notes that, depending on your frame of reference, this may or may not be considered a true error. 
</p>
<p>
His Cognifty framework handles things a bit differently. It allows you to change the presentation handler to redirect to another url if an error like a 404 is thrown - a technically "more correct" way of handling things.
</p>]]></description>
      <pubDate>Tue, 08 Jul 2008 07:51:20 -0500</pubDate>
    </item>
  </channel>
</rss>
