Closing STDOUT should be good enough for the server. Alternatively, if
you know how big the content you are sending is, you can send a
Content-Length header, and assuming the client doesn't ignore that (it
shouldn't), the client will say the page is done when it is.
It might make more sense to
Koms Bomb wrote:
> If I have a cgi script that send text/plain what does the client
see if I send
> all the text at once but then don't exit for seconds because I'm
doing some
> background processing at my end? do they sit and spin around in
circles?
Don't hang the
>
> > If I have a cgi script that send text/plain what does the client see if
> I send
> > all the text at once but then don't exit for seconds because I'm doing
> some
> > background processing at my end? do they sit and spin around in
> circles?
Don't hang the request for long time, otherwise
On 3/25/06, Tom Allison <[EMAIL PROTECTED]> wrote:
> If I have a cgi script that send text/plain what does the client see if I
> send
> all the text at once but then don't exit for seconds because I'm doing some
> background processing at my end? do they sit and spin around in circles?
What ha
If I have a cgi script that send text/plain what does the client see if I send
all the text at once but then don't exit for seconds because I'm doing some
background processing at my end? do they sit and spin around in circles?
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comma
