Re: OScheduler

Mathias Bogaert wrote:

>As Hani mentioned, the API (IMO overall, not only JobStore) seems too
>verbose. Too many methods to implement.
>  
>
No disagreements from me on this comment!   Quartz 2.0 definitely 
attempts to address this - though many features tends to require many 
methods on the APIs.

>Having a lot of features is nice, but the question is 'are all these
>features as useful as they are cool'. RMI support might be nice, but if 1%
>of the users is actually using it, it would be better to put it in a
>quartz-extras subproject.
>
>  
>
This is a very good point, and you guys would be welcome to help keep 
feature-creep in check!  No need to bloat up an API with unused features. 

For interests sake, I happen to know that the RMI feature is used quite 
commonly I would guesstimate by about 15-20% of users.  In fact there 
are honestly only a few small features that aren't in heavy use.

>As with any of the other OS projects, the moment that you have design
>questions or would like feedback on something, the OS developers are there.
>People already discuss a whole lot of topics concerning OS. Check the
>archives. In the end, for most of us this is a learning thing. Although many
>of us are around for quite a while, most of us are perfectionists looking
>for the coolest design, the 'holy grail'. It's addictive.
>
>  
>
Yeah.  That's why I'm psyched about giving the design of Quartz a second-go!

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