Return-Path: Delivered-To: apmail-incubator-geronimo-dev-archive@incubator.apache.org Received: (qmail 37201 invoked by uid 500); 14 Aug 2003 16:41:04 -0000 Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: geronimo-dev@incubator.apache.org Delivered-To: mailing list geronimo-dev@incubator.apache.org Received: (qmail 37188 invoked from network); 14 Aug 2003 16:41:04 -0000 Received: from saturn.opentools.org (HELO www.princetongames.org) (66.250.40.202) by daedalus.apache.org with SMTP; 14 Aug 2003 16:41:04 -0000 Received: from localhost (ammulder@localhost) by www.princetongames.org (8.11.6/8.11.6) with ESMTP id h7EIE6U03270 for ; Thu, 14 Aug 2003 14:14:06 -0400 X-Authentication-Warning: www.princetongames.org: ammulder owned process doing -bs Date: Thu, 14 Aug 2003 14:14:05 -0400 (EDT) From: Aaron Mulder X-X-Sender: ammulder@www.princetongames.org To: geronimo-dev@incubator.apache.org Subject: Re: Timer Service In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 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