<?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, 08 Sep 2008 05:41:38 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[ThinkPHP Blog: Handling large files with(out) PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/5929</guid>
      <link>http://www.phpdeveloper.org/news/5929</link>
      <description><![CDATA[<p>
On the ThinkPHP blog today, there's a <a href="http://blog.thinkphp.de/archives/131-Handling-large-files-without-PHP.html">quick hint</a> about dealing with larger files both with and whithout PHP.
</p>
<blockquote>
As <a href="http://www.microsoft.com/billgates/default.asp">one man</a> <a href="http://groups.google.com/group/alt.folklore.computers/msg/99ce4b0555bf35f4">was quoted</a> "640K of memory should be enough for anybody" no one will need to access more than 2 GB data. What happens if you - just for scientific reasons of course - try to access larger files using your 32bit hardware and your favorite programming language PHP?
</blockquote>
<p>
They <a href="http://blog.thinkphp.de/archives/131-Handling-large-files-without-PHP.html">give the example</a> of opening a large 2 gig file with PHP and the resulting error that would pop up. They try a few differnt ways before getting down to more of a non-PHP PHP solution (yes, you read that right). They decided, instead, to create a script to work with the file chunked, using an exec() call to the unix split command to break it up.
</p>]]></description>
      <pubDate>Wed, 02 Aug 2006 05:47:06 -0500</pubDate>
    </item>
  </channel>
</rss>
