Return-Path: 
 <directory-dev-return-1891-apmail-incubator-directory-dev-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-directory-dev-archive@www.apache.org
Received: (qmail 43870 invoked from network); 10 Sep 2004 19:37:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 10 Sep 2004 19:37:11 -0000
Received: (qmail 72595 invoked by uid 500); 10 Sep 2004 19:37:10 -0000
Delivered-To: apmail-incubator-directory-dev-archive@incubator.apache.org
Received: (qmail 72555 invoked by uid 500); 10 Sep 2004 19:37:10 -0000
Mailing-List: contact directory-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:directory-dev-unsubscribe@incubator.apache.org>
List-Subscribe: <mailto:directory-dev-subscribe@incubator.apache.org>
List-Help: <mailto:directory-dev-help@incubator.apache.org>
List-Post: <mailto:directory-dev@incubator.apache.org>
List-Id: "Apache Directory Developers List"
 <directory-dev.incubator.apache.org>
Reply-To: "Apache Directory Developers List"
 <directory-dev@incubator.apache.org>
Delivered-To: mailing list directory-dev@incubator.apache.org
Received: (qmail 72538 invoked by uid 99); 10 Sep 2004 19:37:10 -0000
X-ASF-Spam-Status: No, hits=0.6 required=10.0
	tests=FROM_ENDS_IN_NUMS,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of aok123@bellsouth.net
 designates 205.152.59.69 as permitted sender)
Received: from [205.152.59.69] (HELO imf21aec.mail.bellsouth.net)
 (205.152.59.69)
  by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 10 Sep 2004 12:37:08 -0700
Received: from mail.bellsouth.net ([205.152.59.156])
          by imf21aec.mail.bellsouth.net
          (InterMail vM.5.01.06.11 201-253-122-130-111-20040605) with SMTP
          id
 <20040910193706.MASL27018.imf21aec.mail.bellsouth.net@mail.bellsouth.net>
          for <directory-dev@incubator.apache.org>;
          Fri, 10 Sep 2004 15:37:06 -0400
X-Mailer: Openwave WebEngine, version 2.8.15 (webedge20-101-1103-20040528)
X-Originating-IP: [65.90.232.2]
From: Alex Karasulu <aok123@bellsouth.net>
Organization: Solarsis Group
To: "Apache Directory Developers List"
 <directory-dev@incubator.apache.org>,'Apache Directory Developers
 List'	 <directory-dev@incubator.apache.org>
Subject: Re: RE: [SEDA] Some questions and idea about current SEDA API design
Date: Fri, 10 Sep 2004 15:37:06 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Message-Id: 
 <20040910193706.MASL27018.imf21aec.mail.bellsouth.net@mail.bellsouth.net>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

> From: "Tenc�, Vincent"
> 	 <vtence@optimuminformatique.com>
> Date: 2004/09/10 Fri PM 02:19:38 EDT
> To: 'Apache Directory Developers List'
> 	 <directory-dev@incubator.apache.org>
> Subject: RE: [SEDA] Some questions and idea about current SEDA API design
> 
> <snip/>
> 
> > > 5. IMHO, SEDA could be separated with multi-layered thread pool for
> > > generic event handling and its networking frontend (e.g. seda-event
> > > and seda-networking). How do you think?
> > 
> 
> <snip/>
>  
> > Anyone else have some thoughts regarding the approach to take?
> 
> To what extent our code overlaps with Berin's code based on Avalon event? Is
> it worth investigating if we can consolidate work here or not? Just asking.

It's basically the same thing really.  If you remember we were going to use it or just fork.  Turns out we do a couple of things a little more differently so there was some divergence but nothing that could not be worked out.  Of course there would be an additional dependency then too.

Alex