|
From: Ivan R. <iv...@we...> - 2003-09-12 19:28:10
|
> Exactly! But I think the list of requirements still needs to be made, > reflecting people's experiences with schedulers... My scheduler requirements are given below. These are based on the implementation I've started some time ago. This is not an attempt to define and replace an "enterprise scheduler". For a nice example of an enterprise class scheduler have a look at Flux, http://www.simscomputing.com/. Scheduler requirements ====================== Immediate --------- * Easy to use (gentle learning curve) * Non intrusive (any object method can be scheduled) * Support for persistent and non-persistent tasks * Crontab compatible syntax (see "man crontab") * Support for runnable interfaces * Support for any object method, with our without parameters * Spring support, scheduling directly from the configuration file * Spring support, events to be scheduled * Pluggable persistence modules * File system storage module (crontab compatible) * Changes to task data in the container will be picked up by the engine * Support for task launchers, eg, execute native binaries, RMI, EJB, XMLRPC, SOAP, etc. Other ----- * Support for seconds (crontab does not support resolution finer than minutes) * JDBC storage module * Misc. launcher implementations * Persisting information between tasks -- ModSecurity (http://www.modsecurity.org) [ Open source IDS for Web applications ] |