Return-Path: Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org Received: (qmail 27472 invoked from network); 13 Jan 2004 23:12:41 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 13 Jan 2004 23:12:41 -0000 Received: (qmail 77235 invoked by uid 500); 13 Jan 2004 23:12:26 -0000 Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org Received: (qmail 77193 invoked by uid 500); 13 Jan 2004 23:12:26 -0000 Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Apache Directory Developers List" Reply-To: "Apache Directory Developers List" Delivered-To: mailing list directory-dev@incubator.apache.org Received: (qmail 77180 invoked from network); 13 Jan 2004 23:12:26 -0000 Received: from unknown (HELO zivix.com) (66.103.225.138) by daedalus.apache.org with SMTP; 13 Jan 2004 23:12:26 -0000 Received: (qmail 42515 invoked by uid 80); 13 Jan 2004 23:06:53 -0000 Received: from 192.251.90.50 ([192.251.90.50]) by horde.thewallacepack.net (Horde) with HTTP for ; Tue, 13 Jan 2004 18:06:53 -0500 Message-ID: <20040113180653.pog04c88scw8wwsg@horde.thewallacepack.net> Date: Tue, 13 Jan 2004 18:06:53 -0500 From: rwallace@thewallacepack.net To: directory-dev@incubator.apache.org Subject: RE: Re: [seda] Re: SEDA References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 192.251.90.50 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Quoting Tim Walker : > This is very interesting. Is the 'Avalonized version of Seda' a rewrite? Any > thoughts on the motivation for > the rewrite in Eve? > > Thanks very much, > The events package isn't so much a rewrite as it is a different approach using the same ideas. I'm no expert on the events package in excalibur but from what I understand it is meant as a more general solution following the Avalon design philosophy (i.e. IoC, etc.). > -- > Tim > > > -----Original Message----- > From: rwallace@thewallacepack.net [mailto:rwallace@thewallacepack.net] > Sent: Tuesday, January 13, 2004 3:02 PM > To: directory-dev@incubator.apache.org > Subject: Re: Re: [seda] Re: SEDA > > Quoting Alex Karasulu : > > > > > That's a good idea I'm sure any protocol server could benefit from > > a generic SEDA API in the commons. I'll look into refactoring out > > the SEDA stuff as I go over that code again while reimplementing Eve's > > front end subsystem. However there really is not much to SEDA IMHO. > > It's one of those ideas where you go, "heck why didn't I think of that." > > A queue, a thread pool, enqueue predicates and a handler is pretty > > striaght forward. I'll work on getting the few classes out there > > once I'm done with the backend stuff into a commons package within > > our SVN repo then you can take a look again. > > > > Alex > > > > I was curious if you plan to do this from scratch or use the Avalon Excalibur > Event package as a basis? It already has most (maybe all?) of what you need > and is an already Avalonized version of SEDA. > > Rich > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.