|
From: Cameron B. <ca...@da...> - 2003-11-03 12:04:47
|
At first I was thinking that the better approach was to include an 'out-of-the-box' plugin for quartz, since it is a system that I have used before. though after reading the Chronos manual, I think that something really simple like that may be a very good idea. I would still like to see spring provide support for Quartz :) Cameron. Ivan Ristic wrote: > >> I don't think Spring should attempt to include a full-featured >> scheduler. > > > I agree with that, except that I wouldn't consider this scheduler to > be full-featured :) Chronos is an attempt at a small library to > satisfy the needs of most people so that they don't have to go out > and learn more complex libraries. > > If you don't think that it should be a part of Spring I have no > problem with that. > > >> However, there is an argument for including a convenient, readily >> available, >> implementation of a scheduler abstraction. This gives the user the >> benefits >> of pluggability in good Spring fashion. > > > We'll see whether someone will come forward. Or, we may attempt to > contact the Quartz people and seek their help/opinion. > -- Any damn fool can write code that a computer can understand... The trick is to write code that humans can understand. [Martin Fowler http://www.martinfowler.com/distributedComputing/refactoring.pdf] |