<?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>Thu, 08 Jan 2009 03:43:18 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Sebastian Bergmann's Blog: Using Bazaar for PHPUnit Development]]></title>
      <guid>http://www.phpdeveloper.org/news/11662</guid>
      <link>http://www.phpdeveloper.org/news/11662</link>
      <description><![CDATA[<p>
In <a href="http://sebastian-bergmann.de/archives/837-Using-Bazaar-for-PHPUnit-Development.html">this new post</a> to his blog <i>Sebastian Bergmann</i> looks at how to use <a href="http://bazaar-vcs.org/">Bazaar</a> (a dstributed version control system) in his development the PHPUnit tool.
</p>
<blockquote>
Last December, when I was in Australia and started to work on the <a href="https://launchpad.net/php-object-freezer">Object_Freezer</a> code, I "dived into" <a href="http://bazaar-vcs.org/">Bazaar</a> (bzr) and learned the value of <a href="http://bazaar-vcs.org/Workflows">local commits</a> as they allow me to work offline, e.g. when disconnected during travel. Thanks to <a href="http://bazaar-vcs.org/BzrForeignBranches/Subversion">bzr-svn</a>, I can now work offline for <a href="http://www.phpunit.de/">PHPUnit</a> development as well.
</blockquote>
<p>
He shares his setup - a local shared repository for branching/trunk work and a linked checkout of PHPUnit between Bazaar and Subversion. This allows him to commit locally with Bazaar and, when he gets back online, issue a "merge" command to make the push back out to Subversion's remote repository.
</p>]]></description>
      <pubDate>Fri, 02 Jan 2009 14:05:02 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Brian Moon's Blog: PHP's MySQL connection timeout]]></title>
      <guid>http://www.phpdeveloper.org/news/9419</guid>
      <link>http://www.phpdeveloper.org/news/9419</link>
      <description><![CDATA[<p>
In the process of debugging one of his scripts, <i>Brian Moon</i> came across a default setting (and problem) in the MySQL extension that didn't seem to <a href="http://doughboy.wordpress.com/2008/01/13/phps-mysql-connection-timeout/">make much sense to him</a>:
</p>
<blockquote>
There are several reasons that PHP could not be able to connect to MySQL. [...] Or, perhaps the entire server is offline.
</blockquote>
<p>
The mysql.connect_timeout setting in the php.ini is supposed to handle this sort of instance, but the default is set tpo 60 seconds. It's only apparently used when the server is completely offline and, in his opinion, is set way too high. He's proposing a patch to the MySQL extension to change this setting's default to shorten it to something a bit more reasonable.
</p>]]></description>
      <pubDate>Mon, 14 Jan 2008 12:59:00 -0600</pubDate>
    </item>
  </channel>
</rss>
