in reply to Response timeout solution

If you need to have the complete response sent within 60 seconds, the first thing I'd do were to stop using CGI.

If you have to just send something within 60 seconds, immediately print out some reply (let's assume 200 OK is good), and keep printing bogus headers until you have the response ready.

Replies are listed 'Best First'.
Re^2: Response timeout solution
by vit (Friar) on Jun 13, 2011 at 23:10 UTC
    If you need to have the complete response sent within 60 seconds, the first thing I'd do were to stop using CGI.

    CGI has nothing to do with that. It's my computations.

    If you have to just send something within 60 seconds, immediately print out some reply (let's assume 200 OK is good), and keep printing bogus headers until you have the response ready.

    This I think is what I probably need. Could you give me an example. Say, there is a loop where I do some computations. How can I push something back to the client in every iteration?
    What do you mean by printing bogus headers?
[reply]

      I mean headers that contribute nothing to the response, just to show the client that "things are still going on". You might need to switch off buffering so that the client sees these headers and gets these as quickly as possible:

      Status: 200 OK
X-Bogus-Header: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
X-Bogus-Header: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
...
X-Bogus-Header: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Content-Type: text/html

<html>
<body>
...

      [download]
[reply]
[d/l]
        You might need to switch off buffering so that the client sees these headers and gets these as quickly as possible:

        How to switch buffering off ?
[reply]
        But my computations which take 60sec+ start after 
        <html>
<body>
...

        [download]
[reply]
[d/l]
[reply]

In Section Seekers of Perl Wisdom