|
|
Posted by ImOk on 07/03/06 01:56
Well, if it makes you feel better (and worse after reading) here isthe
bug report. Its supposed to be fixed, but no one has done anything in a
few years. I am surprised. I guess people jut use Java for issues like
this.
http://bugs.php.net/bug.php?id=27792
Martin wrote:
> Thanks for both your replys.
>
> I have noticed that PHP does not handle big files well in any
> situation. The manual brushes by this and, for example, suggests I use
> sprinf to make an unsigned number to get the correct size for files up
> to 4GB. So very 90s. :)
>
> I am surprised that PHP can't simply get the same result as 'ls'. I was
> thinking of using it but the downside is that it imposes some
> limitations on the server installation I can use. Ideally I would like
> to avoid exec() and other commands that is often blocked on hosting
> servers. (even though most won't like 10Gb files anyway)
>
> The bigger problem is really that different installations return vastly
> different results for filesize(). My local php4 (Mac OS X) at least
> returns a number while the php5 (Fedora) server I use throws a warning
> and returns false on the same file. Php5 on Fedora I really expected to
> be up to it.
>
> Sorry for the little rant. This is one area where I assumed PHP would
> be OK. Developing an application for a few months and at the final
> testing stage finding out these problems is no fun. You can imagine how
> much headscratching I have done to get the uploading and downloading of
> these huge files to work... and then I stumble on this "detail".
>
> Thanks again guys.
Navigation:
[Reply to this message]
|