in reply to Running Perl Continuously

My point to not wanting to refresh the HTML page is to keep from having a new process started every 5 seconds by every user. Those add up fast. However, I also understand that keeping one process going (and opening/closing the database every few seconds) for every user adds up to a lot of system resources.

Another reason for wanting to do this is so that the user doesn't get any flashing on their screen from the script reloading all the time. Smooth, continuous output looks pretty cool.

Any ideas or comments on this?

Replies are listed 'Best First'.
Re: Re: Running Perl Continuously
by mr.dunstan (Monk) on Dec 15, 2001 at 07:04 UTC
    Yeah, I would shy away from trying to server massive amounts of data thru your webserver - the size of the responses will bog your server down.

    Instead - if it's really a -massive- dataset - and you don't need to be serving it up all that fast, you just need to make sure you serve it -all- up when it's requested - how about using email?

    It's pretty reliable and can transmit a ton of data without causing any wierd hiccups. It's also fairly easy to write email parsers that can handle the data import too ...

    My 2 pesos.

    -mr.dunstan
[reply]

In Section Seekers of Perl Wisdom