http://www.perlmonks.org?node_id=127970


in reply to (joealba) 1 hour cgi script?
in thread Detect Stop Button

I think you're making too many assumptions about the user. If it's an "in house" type of "admin tool", it could be some kind of reporting tool so that a manager doesn't have to know how to make MySQL queries. For example, maybe they only need the information on demand about every other month, so it would be wasteful to have a cron job doing an hour of processing every day. You might think just run a command, but some people don't have any idea what that really means, and developers get tired of being command-line (and MySQL :) monkeys.

Replies are listed 'Best First'.
Re: Re: (joealba) 1 hour cgi script?
by joealba (Hermit) on Nov 28, 2001 at 09:30 UTC
    Well, cron jobs can run at any interval.. once a minute, once an hour, once a month... You just make the best choice for the application.

    There is still no good reason for a CGI script to run for 1 hour. Leaving a browser window tied up for that long is a Bad Idea, especially when a browser timeout will stop this lengthy report from running.

    The process could maybe be started through a CGI script, forked off, and then e-mail the user when it is complete. But, it shouldn't sit there running.

    TMTOWTDI, but a 1 hour CGI script is the wrong way.