I've re-implemented the Scheduler as a TurbineService and I've added the
ability
for each Job to run in it's own thread. This means that Jobs will run on
time
regardless if they are still running in a seperate thread. Under these
conditions
it's the programmer's job to make sure they synchronize on any resources
that the Job
may be using. This should only be an issue if a given task is scheduled
to run again
in a time that is < the time it takes to complete. In my mind,this is
more like a cron
type function.
In terms of starting the SchedulerService, I still see the need for it
to be initiated
in the Turbine.init(). Since the Scheduler runs independent of any
Turbine request I don't
know of any other way to make sure that the thread that manages the
queue is started correctly.
If this is a problem, please provide some insight on a better way to do
this.
I have *not* committed these changes yet because I want to complete the
ability to add,remove,and
update jobs with an interface that I'll add to the User admin area. I
hope to do this over the
next few days. In the meantime, if anyone does any work on the
Scheduler, I'd appreciate if
you could ping me so we don't overwrite each other's work.
Stephen - Thanks for your earlier response on the Scheduler stuff and
I'd like to hear if you
have other ideas on a better way to do this.
dave
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
