The "Lines 1 through 3 begin nearly every CGI program I write: enabling taint checking, compiler restrictions, and disabling the buffering of standard output." in your article doesn't hold true any more for Apache 2. Specifically the "$|++;" which does disable the buffering at the perl level but not within Apache v2. :(Uh, you're apparently confused. I'm unbuffering the connection between the forked Perl process and Apache. That doesn't matter whether it's Apache 1 or Apache 2. That's to keep unbuffered and buffered output from intermixing badly to STDOUT, so that the header doesn't appear after some of the body content, for example.
The method to use now is forking the process in the background and providing updates. Roy Johnson provides the link to the redirection discussion.And the technique shown is indeed "fork and continue the process in the background". Did you read the article?
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
In reply to Re^3: Creating a "Progress" page with CGI
by merlyn
in thread Creating a "Progress" page with CGI
by Travis_M
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |