Return-Path: 
 <dev-return-5848-apmail-directory-dev-archive=directory.apache.org@directory.apache.org>
Delivered-To: apmail-directory-dev-archive@www.apache.org
Received: (qmail 27761 invoked from network); 9 May 2005 07:17:55 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 9 May 2005 07:17:55 -0000
Received: (qmail 53353 invoked by uid 500); 9 May 2005 07:20:46 -0000
Delivered-To: apmail-directory-dev-archive@directory.apache.org
Received: (qmail 53237 invoked by uid 500); 9 May 2005 07:20:44 -0000
Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@directory.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@directory.apache.org>
List-Post: <mailto:dev@directory.apache.org>
List-Id: <dev.directory.apache.org>
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Delivered-To: mailing list dev@directory.apache.org
Received: (qmail 53104 invoked by uid 99); 9 May 2005 07:20:41 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=RCVD_BY_IP
X-Spam-Check-By: apache.org
Received-SPF: pass (hermes.apache.org: domain of trustin@gmail.com designates
 64.233.184.199 as permitted sender)
Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.199)
  by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 09 May 2005 00:20:39 -0700
Received: by wproxy.gmail.com with SMTP id 70so2038595wra
        for <dev@directory.apache.org>; Mon, 09 May 2005 00:17:26 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=hQIpOuHxbm0fOJiEn4yDObq+COn/xounqH6EFN7Tm1pAeHC7nBEQYtuea1bOk3SYkcOKnQFtuio7D4SccRX2dFriwiVZFwyb3FQllO78TlXvOKiFEpVmsALN5JC1LVbr16KD72xH5FL/l9ta1PnBvq6OkUz9J/dJ/o2/bXUVUQ4=
Received: by 10.54.70.2 with SMTP id s2mr2454499wra;
        Mon, 09 May 2005 00:17:26 -0700 (PDT)
Received: by 10.54.70.20 with HTTP; Mon, 9 May 2005 00:17:26 -0700 (PDT)
Message-ID: <768dcb2e05050900172285f39b@mail.gmail.com>
Date: Mon, 9 May 2005 16:17:26 +0900
From: Trustin Lee <trustin@gmail.com>
Reply-To: Trustin Lee <trustin@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [mina] Integrating I/O layer and Protocol layer
In-Reply-To: <a8f18ca305050821497cddb624@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <768dcb2e05050816211a8b01b4@mail.gmail.com>
	 <a8f18ca305050821497cddb624@mail.gmail.com>
X-Virus-Checked: Checked
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

Hi Vinod,

Thanks for your fast feedback, I created a branch called
'api_integration'.  I'll let you know when it is ready.

2005/5/9, Vinod Panicker <vinod.p@gmail.com>:
<snip/>
> > 2. Acceptors and Connectors fire messageReceived and messageSent event
> > whose messages are ByteBuffers; users will have to downcast them to
> > ByteBuffers.
>=20
> All the attributes of the "Session" would still be completely configurabl=
e?

Yes of course.

> > This change removes distinction between I/O layer and Protocol layer,
> > and therefore brings us more unified API though users of I/O layer
> > only will have to downcast message objects to ByteBuffers, but I think
> > it doesn't matter actually.
>=20
> I'd actually prefer a bit more flexibility here.  Let me think on this
> a little bit.  Downcasting if u wanna do raw I/O is not really
> desirable.

Yeah downcasting is error prone.  But we did downcasting when we
implement ProtocolHandlers, too.  I'm looking forward to your
solution. :)

Thanks,
Trustin
--=20
what we call human nature is actually human habit
--
http://gleamynode.net/