Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 94769 invoked from network); 3 Feb 2006 14:02:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Feb 2006 14:02:51 -0000 Received: (qmail 78539 invoked by uid 500); 3 Feb 2006 14:02:49 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 78474 invoked by uid 500); 3 Feb 2006 14:02:49 -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 78463 invoked by uid 99); 3 Feb 2006 14:02:48 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2006 06:02:48 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of ajnabee@gmail.com designates 64.233.184.201 as permitted sender) Received: from [64.233.184.201] (HELO wproxy.gmail.com) (64.233.184.201) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2006 06:02:48 -0800 Received: by wproxy.gmail.com with SMTP id i22so592455wra for ; Fri, 03 Feb 2006 06:02:27 -0800 (PST) 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:content-transfer-encoding:content-disposition:references; b=dkALGsZ3uRyIP4amphL6hGQNjvCqptC3jii6zNpO3HPL3KBd2KrU6d8Hm2DINg99l1lq3r6NbYE6Tx4ASCeIWsPaw1M5xuOmIaHYF9dZXQAlS6NQf0o1KIp+G0grWQVtC8BjD9xuqWRsX0gyVjfLCNYhTmLfVsldhzZBhtoLG6g= Received: by 10.64.150.4 with SMTP id x4mr1189449qbd; Fri, 03 Feb 2006 06:02:27 -0800 (PST) Received: by 10.64.201.2 with HTTP; Fri, 3 Feb 2006 06:02:27 -0800 (PST) Message-ID: Date: Fri, 3 Feb 2006 19:32:27 +0530 From: Nirmalya Sengupta To: Apache Directory Developers List Subject: Re: [mina]:In which package can I find ProtocolHandlerAdapter? In-Reply-To: <004e01c6289c$56945a10$0300a8c0@fedechiccowinxp> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <004e01c6289c$56945a10$0300a8c0@fedechiccowinxp> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thank you very much, Fed, for the informaiton. I thought on similar lines but was not sure. I also agree with you on the suggestion, that the filter-chain is by far the best place to implement a codec. I am using 9.0, and while I also assume that such fundamentals are not changed in any which way in 9.1, I will share my experience when I begin to use 9.1. Thanks again Nirmalya On 2/3/06, fedechicco@gmail.com wrote: > I had this problem too, i think that the protocol handler was replaced wi= th > simple IoHandler, and that there are a filter now that implements codecs. > I copied from the examples in the tutorial > http://directory.apache.org/subprojects/network/xref-examples/org/apache/= mina/examples/sumup/ServerSessionHandler.html > and I saw that now this filter is used: > session.getFilterChain().addFirst( "protocolFilter", new > ProtocolCodecFilter( codec ) ); > > Please take a look around on org.apache.mina.filter.codec package that > provide useful already implemented codecs Filter. > > All these informations are valid for MINA 9.0, for other versions I don't > know, but I think they are still valid for 9.1 > > by Fed > > -- Nirmalya Sengupta Software Technologist "If you have built castles in the air, your work need not be lost. That is where they should be. Now put the foundation under them." --Henry David Thoreau