Re: OScheduler

Hani Suleiman wrote:

> On Jan 11, 2004, at 6:38 PM, James House wrote:
>
> *snip*
>
>> work to go, since it is a serious refactoring.   Both the existing 
>> (1.x) design and the 2.0 design support plugable persistence.  There 
>> is currently RAM and JDBC-based persistence (a bit of an oxymoron 
>> with RAM).  Also there is a mechanism to use XML files to 
>> auto-populate jobs in the RAM store during initialization.
>>
> Incidentally, last time I looked at it, there was far, far, far too 
> many methods that a persistence store had to implement, hopefully this 
> is a bit simplified in 2.0!

Yeah... but probably not as much as you'd like ;-)  Most of that stuff 
was there for a reason after all!  I've struggled a fair amount with 
this, and have tried to balance number of interfaces against number of 
methods on a single interface.  Of course, architecture itself plays a 
role in how clean all of this works out. 

>> If the OS community is willing to have Quartz, I'll first need to run 
>> it by a few of the other people over on the Quartz project, who ought 
>> to at least have a little say about it. 
>
> Well it definitely has my +1 


It sounds like (from you and the other responders), that you're all 
willing to have Quartz as a part of OpenSymphony.  I'll make a decision 
soon - after I get some comments from a couple particular Quartz 
contributors.

james




-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html