Shouldn't each JobEntry extend java.lang.Thread?
I think it should. Specifically because if JobScheduler encounters an
entry that takes a very long time to run it may not get to other entries
before they are supposed to run.
Also, what if you have two JobEntries that run at the same time.
A way around this would be to have a wrapper thread that you give it a
job entry as a constructor.
Just some thoughts. I need to get Job scheduler working for Jetspeed
and want to make sure everyone is on the same page here.
Thoughts?
--
Kevin A Burton
http://relativity.yi.org
Linux - The revolution will NOT be televised
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
