Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates
 66.249.92.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=D/8sSU0X0AVICIXlAeLdc6iSg/L6o4GYMZlISdHIv/NRvmBlNzB67dugVieds7nDFqe0g/LU09jQ83BgoD3S0VfuYK8RvO76HYlJmc2ThKSirBt74Xq7e/Syy07AYekuRsw7CtiL3YEKQnkhU3W0VjgPhD4pkEfhPdQNKNHHVmE=
Message-ID: <768dcb2e0601222106h3f7197d2n@mail.gmail.com>
Date: Mon, 23 Jan 2006 14:06:07 +0900
From: Trustin Lee <trustin@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [mina] Introducing the New API for 0.9.1.
In-Reply-To: <NBBBJGEAGJAKLIDBKJOPIEBJGAAC.noel@devtech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_14196_20290941.1137992767632"
References: <86CCC348-CC61-484A-B1F2-62B3B320FDB2@apache.org>
	 <NBBBJGEAGJAKLIDBKJOPIEBJGAAC.noel@devtech.com>

------=_Part_14196_20290941.1137992767632
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2006/1/23, Noel J. Bergman <noel@devtech.com>:
>
> Peter,
>
> > The changes look like they help simplify usage of MINA in simple
> > scenarios.. the examples are certainly much simpler, but for users
> > that might have a more complex integration, they seem to be somewhat
> > of a step backwards
>
> I haven't looked at the code, but having seen the dialog so far, you
> certainly make a strong case for vetoing the changes until your concerns
> are resolved.
>
> Perhaps a set of convenience classes for MINA would address ease of use
> without sacrificing more advanced use.


Sure.  We do our best to fulfill the needs of various users as usual.  This
API is not a final version but a draft.  The final shape we will get with
MINA 1.0.0 will satisfy as many users as possible.

Thank you,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
PGP Key ID: 0x854B996C

------=_Part_14196_20290941.1137992767632
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2006/1/23, Noel J. Bergman &lt;<a href=3D"mailto:noel@devtech.com">noel@dev=
tech.com</a>&gt;:<div><span class=3D"gmail_quote"></span><blockquote class=
=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin=
: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Peter,<br><br>&gt; The changes look like they help simplify usage of MINA i=
n simple<br>&gt; scenarios.. the examples are certainly much simpler, but f=
or users<br>&gt; that might have a more complex integration, they seem to b=
e somewhat
<br>&gt; of a step backwards<br><br>I haven't looked at the code, but havin=
g seen the dialog so far, you<br>certainly make a strong case for vetoing t=
he changes until your concerns<br>are resolved.<br><br>Perhaps a set of con=
venience classes for MINA would address ease of use
<br>without sacrificing more advanced use.</blockquote><div><br>Sure.&nbsp;=
 We do our best to fulfill the needs of various users as usual.&nbsp; This =
API is not a final version but a draft.&nbsp; The final shape we will get w=
ith MINA 1.0.0
 will satisfy as many users as possible.<br><br>Thank you,<br>Trustin</div>=
</div>-- <br>what we call human nature is actually human habit<br>--<br><a =
href=3D"http://gleamynode.net/">http://gleamynode.net/</a><br>PGP Key ID: 0=
x854B996C

------=_Part_14196_20290941.1137992767632--