Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 90963 invoked from network); 12 Sep 2005 01:38:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Sep 2005 01:38:44 -0000 Received: (qmail 35526 invoked by uid 500); 12 Sep 2005 01:38:43 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 35467 invoked by uid 500); 12 Sep 2005 01:38:42 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 35450 invoked by uid 99); 12 Sep 2005 01:38:42 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Sep 2005 18:38:42 -0700 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=HTML_30_40,HTML_MESSAGE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS,URIBL_SBL X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of trustin@gmail.com designates 64.233.184.195 as permitted sender) Received: from [64.233.184.195] (HELO wproxy.gmail.com) (64.233.184.195) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Sep 2005 18:38:53 -0700 Received: by wproxy.gmail.com with SMTP id 70so1756211wra for ; Sun, 11 Sep 2005 18:38:40 -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:cc:in-reply-to:mime-version:content-type:references; b=N0WFHdtbCaRIaVHIwdkw8kMEYNTW/hQ0Y3rCWVamXt63l0Sk9bnrpJKDevXHBQZZ+Y9tN9U+oRq4joH9jSznE4aCjyniBPYkDx3iHgL/QOP8fGQzgF57aBAalG0IrM/HfUQvqlR+46A8JRcjSjKkyIp1mbM6p+o7KLYbVW02/x0= Received: by 10.54.5.41 with SMTP id 41mr2158785wre; Sun, 11 Sep 2005 18:38:40 -0700 (PDT) Received: by 10.54.71.11 with HTTP; Sun, 11 Sep 2005 18:38:40 -0700 (PDT) Message-ID: <768dcb2e050911183866288a9e@mail.gmail.com> Date: Mon, 12 Sep 2005 10:38:40 +0900 From: Trustin Lee Reply-To: trustin@gmail.com To: Apache Directory Developers List Subject: Re: MINA Cc: ttm@online.no In-Reply-To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_1687_867206.1126489120051" References: X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_1687_867206.1126489120051 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Thomas, 2005/9/9, Thomas Muller : >=20 > Sorry for the intrusion - just wanted to give my praise to MINA - what a > fantastic API! Definately the best I've seen since Dough Lea's Concurrenc= y > API. Thank you for your encouragement. :)=20 I already made a generic TCP/IP session API that helps implementing > request/response based protocols (with sequence Ids) - MINA fitted in ver= y > nicely. In the future I might extend MINA itself with this functionality, > but for the time being it was easiest the use MINA in the implementation > sections (i.e. further down the inheritance tree). For starters, I can se= e > there will be a problem with extending the MINA sessions (in a=20 > non-intrusive > manner) since there are no SessionFactory classes. Can I see how you implemented it so that I can merge the feature into MINA?= =20 I appreciate that MINA is still in a pre 1.0 release, but if I may make a > suggestion, the SocketConnector class should be extended to handle SOCKS= =20 > and > SSL over SOCKS. Could you explain about SOCKS support on SocketConnector? I don't know how= =20 it can be integrated to SocketConnector. But I think we can implement SOCKS= =20 support as a filter just like we did to support SSL. Thanks, Trustin --=20 what we call human nature is actually human habit -- http://gleamynode.net/ ------=_Part_1687_867206.1126489120051 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Thomas,

2005/9/9, Thomas Muller = <ttm@online.no>: Sorry for the intrusion - just wanted to give my praise to MINA - what afantastic API! Definately the best I've seen since Dough Lea's Concurrency=
API.

Thank you for your encouragement. :)

I alrea= dy made a generic TCP/IP session API that helps implementing
request/res= ponse based protocols (with sequence Ids) - MINA fitted in very
nicely. In the future I might extend MINA itself with this functionalit= y,
but for the time being it was easiest the use MINA in the implementat= ion
sections (i.e. further down the inheritance tree). For starters, I c= an see
there will be a problem with extending the MINA sessions (in a non-intr= usive
manner) since there are no SessionFactory classes.

Can I see how you implemented it so that I can merge the feature into MINA?=

I appre= ciate that MINA is still in a pre 1.0 release, but if I may make a
sugge= stion, the SocketConnector class should be extended to handle SOCKS and
SSL over SOCKS.

Could you explain about SOCKS support on SocketConnector?  I don't know how it can be integrated to SocketConnector.  But I think we can implement SOCKS support as a filter just like we did to support SSL.
Thanks,
Trustin
--
what we call human nature is actually human habit
--<= br>http://gleamynode.net/ ------=_Part_1687_867206.1126489120051--