in reply to Gas gauge ??

Inflicting things on the browser is javascript's job. The cgi server has no connection with the user's browser except for what's in the web page. See perldoc CGI for help on writing javascript from perl. It's no big trick - you just write it along with the rest of the text.

You might look at "server push", but that's an old idea nobody liked.

Update: I forgot, at first, that if you haven't finished printing the page, you can print messages to it periodically.

After Compline,
Zaxo

Replies are listed 'Best First'.
Re: Re: Gas gauge ??
by peterr (Scribe) on Jan 08, 2004 at 03:06 UTC
    Hi Zaxo,

    Thanks for the link to "CGI, there were some interesting examples there about how to use JS. I guess my post is two-fold, one is to inform the user some way (gas gauge, JS,etc), and the other is to continue processing, even if the user presses 'stop' or closes the browser window. I think sometimes they are getting too impatient and just exiting, thinking that everything is done. Ideally, I would like to give them the opportunity to close/exit after they press the "Confirm/submit" button, and simply continue doing all the processing. The logs at present indicate some users have no idea that it is still 'processing'.

    I have been reading this node on Lauching multiple processes, which may be the way to go (spawn a child process) ?

    Thanks,

    Peter

[reply]

In Section Seekers of Perl Wisdom