Ask Bjoern Hansen wrote:
> So: What is the task at hand (more than "run something at certain
> intervals" (which is what cron(8) is for)).
I am building a web something-something (I don't know what's the current
buzzword for that, you know, the big integrated things) similar to the
ArsDigita Community System (ah, I bet this helped a lot more! :-) ).
My first occurence of this need was about expiring session keys from the
database. At first, I was about to do a little query that run from a
cleanup handler every so many seconds, but after that, I was stealing
some more ideas from ACS (it's a very good idea, but AOLserver and Tcl,
ick!), and I was getting jealous of the AOLserver scheduler, which they
use abundantly.
For example, you can check a list of URLs at regular interval to see if
your machines are up (and get a warning if some are not), or you can
send warnings to users when their car is about to get towed away because
of parking regulations. :-)
Anyway, from fussing around in ACS, it came to me that a general
scheduler is a pretty good idea, so I set to it.
More about the rationale in another reply to Matt Sergeant...
> [1] http://perl.plover.com/Questions.html
Very good one, I almost died of a chocolate-covered banana indigestion.
:-)
--
"The 3 great virtues of a programmer: laziness, impatience and hubris."
-- Larry Wall
