On Dec 30, 2004, at 1:54 PM, Denzil Kruse wrote:


--- Bob Showalter <[EMAIL PROTECTED]> wrote: <snip>
Is there a way to tell the browser to hang around
a
bit longer to wait for a response?  Or is there
another way to keep the browser's attention so it
knows it has a "live connection" and to wait?

One way is to have the CGI script output some data periodically.

I tried that, but it didn't matter much. What happens is I have a link. When I click on it, the browser hangs. If I switch to another application on my desktop whose window covers the browser, and then I switch back to the browser, the graphics of the browser is not redrawn. I use IE, and the windows logo isn't spinning and and green progress bar is going nowhere.

Then, after about 30 seconds, the browser recieves
some partial html code and stops.  The html is cut
off, and doesn't correspond to the point in the code
where the time consuming loop is.  I see the process
still going on the server, and know it completes
everything it is supposed to.

I checked the apache conf file, and Timeout is set to
300.  I don't know if that's the right variable for
this.  Why would it cut out after only 30 seconds?

If I'm not mistaken, there may be some buffering going on, so what you see on your browser may not be what has actually been "sent"; it may be buffered. You may want to consider turning off buffering for the block. I've never had the issue, but others may be able to comment on buffering and how it relates to cgi scripts.


Sean


-- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>




Reply via email to