At 10:06  22/3/01 -0700, James House wrote:
>>> Project 1: an Enterprise Job Scheduler
>>> =====================================
>>For #1: Taking the best parts from Avalon and Turbine and merging them into
>>a Commons would be good.
>>
>
>I have not looked far into the Schedulers in Avalon or Turbine - but I think
>that they currently fall quite short of the features features I listed. I
>also don't beleive they are 'organized' in a way that easily fators into
>what I want to build (not to say they wouldn't offer a wealth of code to
>start out with).

Well the parts in Avalon CVS are the "base" of my cron job server that did
most of what you wanted ;)

>From memory the other blocks I created were

PersistentJobStore - stores job definitions and scheduling
JobDispatcher - ie used the job defintions to create list of ant tasks and
execute them
SubjectManager - ie had the subjects/principles and their associated
permissions
CronScheduler - Manager all the rest of the components

Except for SubjectManager (which was an absolute PITA) all the rest are
relatively easy to implement. We had both a DB based PersistentJobStore and
a file based PersistentJobStore. 

The only reason it is not free software/opensource at the moment is because
(a) it relies on a very very ugly fork of ant code  (enough that I am
ashamed to call it my own ;])
(b) I don't have sole copyright on most of it ;( 

As soon as the task engine for ant2.0 is complete I will rebuild it again
though ;) It is largely comparable to fluxs server but it did not have some
of the more complex stuff (they had automatic notification/events for
certain cron events IIRC). Any it will be hosted in Avalon/Phoenix ;)

Cheers,

Pete

*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof."                   |
|              - John Kenneth Galbraith               |
*-----------------------------------------------------*


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to