I'm not entirely sure if this would be the optimal solution in your case, but the way I think this might work is if you were to fork off a child process to handle the file writing part. This would allow you to free up the main process to finish rendering the page to the web client and thereby avoid the time out message.
The code might look something like this (not tested! :):
if (!fork) { # doing stuff in child process...
# open your file handle here
while (my $bytesread = read($filesource, my $buffer,1024))
{
print OUTFILE $buffer;
}
# you could also write to a 'status' file and display that back to t
+he client ;)
exit;
}
print $cgi->header();
print "Your upload is in process... see this status.html page for the
+status (changes every once in awhile :)\n";
exit;
_____________________
$"=q;grep;;$,=q"grep";for(`find . -name ".saves*~"`){s;$/;;;/(.*-(\d+)
+-.*)$/;
$_=["ps -e -o pid | "," $2 | "," -v "," "];`@$_`?{print"+ $1"}:{print"
+- $1"}&&`rm $1`;
print$\;}
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.