On Thu, 21 Oct 1999, Tobias Hoellrich wrote:
> And yet another one (which I used for one project): Detach the process from
> the Apache cgi (no don't use fork inside your script) and have the process
> do its work in the background outputting progress information into a know
> location. Have your web-page reload every minute or less, read the progress
> information and display it to the user. If your script finally completes
> the report have the next reload report the information.
For a detailed info about the approach Tobias is talking about see:
http://perl.apache.org/guide/performance.html#Forking_or_Executing_subprocesse
>
> Tobias
>
> At 06:18 PM 10/21/99 -0700, Jeffrey Baker wrote:
> >Another workable solution is to make the reports in real time, but
> >deliver them by email. Use the web interface to initiate the reporting
> >process and send a confirmation.
> >
> >Cheers,
> >Jeffrey
> >--
> >Jeffrey W. Baker * [EMAIL PROTECTED]
> >Critical Path, Inc. * we handle the world's email * www.cp.net
> >415.808.8807
>
>
>
_______________________________________________________________________
Stas Bekman mailto:[EMAIL PROTECTED] www.singlesheaven.com/stas
Perl,CGI,Apache,Linux,Web,Java,PC at www.singlesheaven.com/stas/TULARC
www.apache.org & www.perl.com == www.modperl.com || perl.apache.org
single o-> + single o-+ = singlesheaven http://www.singlesheaven.com
