You mean like cron? :) and at?
(Subtle suggestion for functional requirements and interface) maybe needs something like an ObjectModel Map? a CronoModel? This could be used to store shared/persistent 'business' data. David > I was proposing exactly this: unifying all 'clock-depending' > events into > a single 'hardbeat' thread where components can register to have their > own 'interrupt' executed. > > It's for sure more elegant than what we have today. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
