|Problems? Is your data what you think it is?
Do the replies to Managing a long running server side process using CGI help?
There's a lot to go through there, but I am trying to avoid the CRON path. Just seems kludgy to me
However a thought hit me, and I'll have to reread the link you posted a few times to see if it's in there:
Is it possible to have a perl script, initiated from a browser, manually construct the proper HTTP::Response, and send it in the middle of my perl script? Theoretically, that would free the browser at the client end, and the rest of the perl script would contain the child code, which has no output, and keeps on running till completion.
Is such a beast possible? And even if so, how dangerous would it be?
That's a lot of "ifs" but just trying to look at it from a different perspective
In reply to Re^2: Can I have a Perl script, initiated from a browser, fork itself, and not wait for the child to end?