<?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>Tue, 08 Jul 2008 22:56:52 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[SitePoint PHP Blog: Dealing with Dependencies]]></title>
      <guid>http://www.phpdeveloper.org/news/9561</guid>
      <link>http://www.phpdeveloper.org/news/9561</link>
      <description><![CDATA[<p>
On the SitePoint PHP blog today, <i>Troels Knak-Nielsen</i> has <a href="http://www.sitepoint.com/blogs/2008/02/04/dealing-with-dependencies/">written up an article</a> that talks about dependencies in your applications - those little interconnections your code relies on to do more with less.
</p>
<blockquote>
In lack of better words, I'll call this compositional programming style. It's a style which is usually more prevalent with experienced programmers. [...] There is, however, a dark side to composition - dependencies.
</blockquote>
<p>
He <a href="http://www.sitepoint.com/blogs/2008/02/04/dealing-with-dependencies/">starts</a> with a definition to bring everyone up to a level field then moves on to how their used (through a "global symbol" or directly passed in) and how they can "leak" if you're not careful. 
</p>
<p>
To help protect you and your code from any kind of damage down the line, <i>Troels</i> suggests making a container to keep objects where they need to be. He even includes an example with namespace support to make things even easier down the road.
</p>]]></description>
      <pubDate>Mon, 04 Feb 2008 12:09:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Christopher Jones' Blog: Temporary LOBS in PHP's OCI8 Extension. Instant Client.]]></title>
      <guid>http://www.phpdeveloper.org/news/9460</guid>
      <link>http://www.phpdeveloper.org/news/9460</link>
      <description><![CDATA[<p>
<i>Christopher Jones</i> talks today on <a href="http://blogs.oracle.com/opal/2008/01/17#a264">his blog</a> about a bug he's just corrected and integrated into the release of the Oracle Instant Client that lets PHP correctly take advantage of the temporary LOBS functionality.
</p>
<blockquote>
When PHP is done with the temporary LOB, it needs to tell Oracle to destroy it. If this isn't done, then the temporary LOB will hang around using DB space until the connection is closed. I just merged a fix worked on by Krishna Mohan and myself for <a href="http://bugs.php.net/bug.php?id=43497">bug 43497</a>.
</blockquote>
<p>
Example code is included showing two instances of its use - a normal use that frees the memory correctly and the other showing how to create the temporary lob to hold the data as needed.
</p>]]></description>
      <pubDate>Mon, 21 Jan 2008 12:05:00 -0600</pubDate>
    </item>
  </channel>
</rss>
