Maybe Quartz is overkill. But if you ship it with hsqldb I don't think there is 
a big issue with the creation of database tables. I have read some blogs 
(http://www.freeroller.net/page/fate/ look at august 05) that Quartz isn't that 
optimized. Maybe we should write something ourselves, maybe not. I will dig in 
to this subject during the weekend, do some tests and perheps write my 
implementation for comparsion.

/Klas

----- Original Message -----
From: Aaron Mulder <[EMAIL PROTECTED]>
Date: Thu, 14 Aug 2003 14:14:05 -0400 (EDT)
To: [EMAIL PROTECTED]
Subject: Re: Timer Service

> On Thu, 14 Aug 2003, Jeremy Boynes wrote:
> > Please review the spec in detail - the EJB Timer Service has requirements
> > for persistent timers and IIRC notifications for events that happened when
> > the server was down.
> 
>       True, but I think we could write something simple using a file for
> persistence and java.util.Timer if we wanted to meet the minimum
> requirements.  There is no facility in the spec for cron-style scheduling
> -- the only scheduling options are millisecond offsets, IIRC.  Granted, we
> could certainly integrate a fancier package and offer more "value added"
> features.  I'm trying to say I don't think we *need* to go there unless we
> want to.
> 
> Aaron
> 

-- 
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr

Powered by Outblaze

Reply via email to