<?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, 13 Oct 2008 09:00:34 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Isolated (and Parallel) Test Execution]]></title>
      <guid>http://www.phpdeveloper.org/news/9281</guid>
      <link>http://www.phpdeveloper.org/news/9281</link>
      <description><![CDATA[<p>
<i>Sebastian Bergmann</i> <a href="http://sebastian-bergmann.de/archives/730-Isolated-and-Parallel-Test-Execution.html">points out</a> a new feature that <a href="http://www.phpunit.de/">PHPUnit</a> (the popular PHP unit testing tool) now has - <a href="http://www.phpunit.de/browser/phpunit/branches/feature/parallel_test_execution">parallel_test_execution</a> allowing for each test to execute on a separate PHP process.
</p>
<blockquote>
The advantages of this include full test isolation and the fact that a test can now cause a PHP fatal error or even a segmentation fault of the PHP interpreter without interrupting the test execution.
</blockquote>
<p>
He does mention, however, that it can cause a bit more overhead for larger testing suites since it needs to create a new process (complete with memory usage) for each running test. There are also coding issues that could be thrown off by this option (he gives an example of an inheritance issue with eZ Components).  
</p>
<p>
He also notes some of his thoughts on how to control/configure the process (like in a configuration file) and via an "@isolated" notation to make it easy to do it dynamically.
</p>]]></description>
      <pubDate>Wed, 19 Dec 2007 15:26:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[DevShed: Working with Multiple Template Files to Separate Logic from Presentation (Part 3)]]></title>
      <guid>http://www.phpdeveloper.org/news/5383</guid>
      <link>http://www.phpdeveloper.org/news/5383</link>
      <description><![CDATA[<p>
Wrapping up their series on "Seperating logic from presentation", DevShed has posted <a href="http://www.devshed.com/c/a/PHP/Working-with-Multiple-Template-Files-to-Separate-Logic-from-Presentation/">this final article</a> capping off the creation of a simple template parser in PHP5.
</p>
<quote>
<i>
By returning to the subject of this last installment, I'll use the skeleton of the original "TemplateProcessor" class to develop an improved, production-level template processor, which, as you'll see in a few moments, will be capable of working with multiple template files, in addition to implementing a chunked caching system. In this way, the class will be able to use several templates that have distinct cache expiration times, aside from utilizing most of the template processing features that you learned before.
</i>
</quote>
<p>
If you haven't read up on them yet, go back and check out <a href="http://www.phpdeveloper.org/news/5289">part one</a> and <a href="http://www.devshed.com/c/a/PHP/Using-a-Template-Processor-Class-in-PHP-5/">part two</a> of the series to catch up. They'll give you the foundation to build from - not just the code but the concepts as well. This <a href="http://www.devshed.com/c/a/PHP/Working-with-Multiple-Template-Files-to-Separate-Logic-from-Presentation/">third part</a> demonstrates chunked caching of your templates/pages as well as pulling in more than one template file at a time. Throw that all together with the functionality from before and you have an extensible, simple template parsing class they use in a bit more concrete example.
</p>]]></description>
      <pubDate>Wed, 17 May 2006 06:07:46 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Jonnay's Blog: REST and URI Names]]></title>
      <guid>http://www.phpdeveloper.org/news/5252</guid>
      <link>http://www.phpdeveloper.org/news/5252</link>
      <description><![CDATA[<p>
On his blog, <i>Jannay</i> briefly shares some of <a href="http://blog.jonnay.net/archives/700-REST-and-URI-names..html">REST and PHP</a> after reading an older <a href="http://www.sitepoint.com/blogs/2005/11/22/who-gets-rest/">post</a> on the SitePoint PHP blog.
</p>
<quote>
<i>
<p>
I've been reading this blog over at sitepoint about Who Gets Rest by PHP heavy Harry Fuecks. It is a fairly link-heavy top level view of what REST is.
</p><p>
Its nice to see more the PHP guys get into REST, as far as PHP guys go, Harry is pretty <a href="http://www.phppatterns.com/">Heavy</a>. What harry has to say about URI naming schemes (especially in the comment section) really helped to gel a very important part of REST for me.
</p>
</i>
</quote>
<p>
He <a href="http://blog.jonnay.net/archives/700-REST-and-URI-names..html">comments</a> that <i>Harry</i>'s ideas about seperation of "tools" from the resources they work with is a very appealing idea, and one that would allow much more flexibility in PHP applications.
</p>]]></description>
      <pubDate>Thu, 27 Apr 2006 06:53:22 -0500</pubDate>
    </item>
  </channel>
</rss>
