in reply to forking large file uploads
This suggests that putting my $req = new CGI; only in the child process might fix your problem. However, I would very surprised if that works. You need the client's browser to run two requests at the same time: one which is uploading the file and another which is querying the status of the upload. The querying request will be the 'visible' one whereas the uploading one is hidden (if only for aesthetic purposes.) So I think it's the client's browser which has to fork() (in a sense). When the file upload is initiated, the browser has to create another page (via javascript) which queries the status of the upload periodically. The file upload request isn't going to display the page returned to it until the file upload is complete.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: forking large file uploads
by sstevens (Scribe) on Jan 23, 2008 at 14:14 UTC |