Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 4815 invoked from network); 23 Jun 2007 11:30:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Jun 2007 11:30:26 -0000 Received: (qmail 82754 invoked by uid 500); 23 Jun 2007 11:30:29 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 82637 invoked by uid 500); 23 Jun 2007 11:30:29 -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 82626 invoked by uid 99); 23 Jun 2007 11:30:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Jun 2007 04:30:29 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates 64.233.166.178 as permitted sender) Received: from [64.233.166.178] (HELO py-out-1112.google.com) (64.233.166.178) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Jun 2007 04:30:25 -0700 Received: by py-out-1112.google.com with SMTP id a73so139125pye for ; Sat, 23 Jun 2007 04:30:04 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=XKrDcOglbRWP//XAdrA6/g9ahb62xzu9iwyK9eX/hppMJcJ/N4Z1KMJS6l2BFYTuFOhooiDMuJTBp3P3DSD5jEgVpPlljMpIQJXsaBz2nMgKuG0qNCLP9R7ll8cWBrVEdGSOuKoWd4jMTpVkD4eEPNdf+tHpf5vi1psW/+Uk5fw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=OXCKHYeeDJkc/0kqjYdZyP/Zl1E1MfZmnuKhckhl0fftTGycEYagERiUV9CAFvzdty+QdEyx+36R24BuChED63wrS91D8OO6JAu4vd4y5mmSwzk5hHyK1gf0TB0uMflYvwf5sS0+/LhIhjm4cP/lnNjEBOoL0fUOfuaUFS5895s= Received: by 10.142.188.11 with SMTP id l11mr77260wff.1182598203847; Sat, 23 Jun 2007 04:30:03 -0700 (PDT) Received: by 10.142.77.21 with HTTP; Sat, 23 Jun 2007 04:30:03 -0700 (PDT) Message-ID: Date: Sat, 23 Jun 2007 13:30:03 +0200 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: Re: Moving from IoHandlerChain to something easier to debug In-Reply-To: <467B07ED.6080702@apache.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_107507_21904949.1182598203828" References: <568753d90706211116v28a9d550mfd6aaa6cf51ccb14@mail.gmail.com> <467B07ED.6080702@apache.org> X-Google-Sender-Auth: b9e0deb65c6ce4a3 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_107507_21904949.1182598203828 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On 6/22/07, Emmanuel Lecharny wrote: > > Enrique Rodriguez a =E9crit : SNIP .. > On 6/21/07, Emmanuel Lecharny wrote: > > It would help MINA developers to know > > whether to use the IoHandlerChain or not. > > If you are going to use a Chain patter, then I guess that the important > point is to think about the problem it solves. For instance, monitoring > by inserting loggers could be a good usage. But the main advantage of > chain parttern is its versatility : you can change the order of > handlers, or simply add or remove handlers on demand. If you never do > that, then using a chain pattern is questionable (IMHO). With MINA filters I think we can still achieve the level of logging that you're talking about but perhaps not at the same resolution so I think the dynamism we gai= n from the chain pattern is somewhat redundant. I don't think it's necessary here since the protocol is relatively static. Actually the chain pattern might benefit LDAP more since it can introduce new mechanisms for things like SASL, Controls, and extended operations but there might be more manageable patterns for this. Alex ------=_Part_107507_21904949.1182598203828 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline

On 6/22/07, Emmanuel Lecharny <e= lecharny@apache.org> wrote:
Enrique Rodriguez a =E9crit :

SNIP ..

> On 6/21/07, Em= manuel Lecharny < elecharny@gmail.com> wrote:> It would help MINA developers to know
> whether to use the IoH= andlerChain or not.

If you are going to use a Chain patter, then I g= uess that the important
point is to think about the problem it solves. For instance, monitoring=
by inserting loggers could be a good usage. But the main advantage ofchain parttern is its versatility : you can change the order of
handle= rs, or simply add or remove handlers on demand. If you never do
that, then using a chain pattern is questionable (IMHO).
With MINA filters I think we can still achieve the level of logging = that you're talking
about but perhaps not at the same resolution so = I think the dynamism we gain
from the chain pattern is somewhat redundant.  I don't think i= t's necessary here
since the protocol is relatively static.  Ac= tually the chain pattern might benefit
LDAP more since it can introduce = new mechanisms for things like SASL, Controls,
and extended operations  but there might be more manageable patter= ns for this.

Alex

------=_Part_107507_21904949.1182598203828--