in reply to Re: Execute with No wait
in thread Execute with No wait

That'll work only if the script also forks. The webserver won't release the browser until the CGI script has exited.

-- Randal L. Schwartz, Perl hacker

Replies are listed 'Best First'.
RE: RE: Re: Execute with No wait
by extremely (Priest) on Aug 24, 2000 at 23:55 UTC

    Actually, that behavior depends on the Webserver and OS. As I recall you can close STDOUT and STDERR under Apache on a Unix'ish box and Apache will dump the other end. Tho a quick test reveals that it also kills the cgi too so it is of little use to the original poster =)

    Does anyone remember if there is a way to make Apache leave the child alive after closing the connection? I have spent too much time in mod_perl so I may have that on the brain.

    --
    $you = new YOU;
    honk() if $you->love(perl)

        Gah =)
        What I was talking about was the cleanup handler stuff in mod_perl where you could "hang-up" the socket connection and then continue to process after the hang-up but before returning the child httpd to the pool.

        Also, this reply is so late from the last post because I never noticed the chatterbox telling me there was a reply. =P Maybe someone should take exp away from me.

        --
        $you = new YOU;
        honk() if $you->love(perl)

RE: RE: Re: Execute with No wait
by bp (Novice) on Aug 25, 2000 at 00:15 UTC
    merlyn, I'm starting to get the picture. Please see my post below.