This is an interesting question, but I must be missing something:
If I understand you right, you're trying to get a large file from
the client (browser) side to your (the server) side. And you
want the user's browser (possibly with the aid of code you
provide) to cooperate in this endeavor so you can get past
the usual (including timeout) limitations.
But javascript (really the only thing available generically) on
the client side does not have access to the user's disk. So
I am curious to know what I am not understanding here.
If browsers are not involved, then I would turn to cURL
within command line PHP (on the client side) or a similar
variant and have the PHP on the Apache end reassemble
the file. Haven't done it, but it seems straightforward.
Probably would try with a command line version of cURL.
As for progress bar, on the client side, you can use COM
methods on recent Windows systems to put up an IE and
keep changing the IE page as you progress along (see the
php.net/com area for starter examples).
Csaba Gabor from Vienna
<jo**********@sagitta-ps.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...
I have to prepare an Apache/PHP based (or perl if easier) web
page that allows a user to upload very large files, possibly
over 10 Gbytes and maybe up to 100 Gbytes.
I'm aware that file upload limits can be increased by config
changes; but I'd rather minimize the need for changes like
this, both for admin reasons and to avoid possible (?) memory problems
or even bugs.
In principle there's a simple solution whereby the user runs
an initial page, in which they input the file name, and the
Submit button then runs JavaScript in the page.
The JavaScript opens the file, positions at a start offset
(initially zero), and reads and uploads up to a fixed length
of the contents, along with a continuation offset (or zero
to indicate the end reached), and the server code re-runs
the script in a loop while this returned offset is non-zero.
Subsequent runs of the script would bypass the data input
and execute the JavaScript directly.
Anyway, the question I have is whether anyone has written
anything similar, ideally with a progress bar?
The only problem I anticipate is possible delays, and even
timeouts, while the code (client or server) positions to
the next offset to read or write (respectively) the next
chunk of a very large, e.g. 50 GByte, file.
Any suggestions gratefully received.
(It's a shame Apache doesn't seem to have an embedded FTP
server in some way. I guess FTP would be the obvious choice,
but the client doesn't wish to have a separate FTP server
running.)
Cheers
John R Ramsden (jramsden at glassouse.com)
