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 (herse.apache.org: domain of elecharny@gmail.com designates
 66.249.92.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=MRScL9aA/wV7IVZE3p7AaDz/Dp9ja2QUfF1m8/o5Rf0zq1ezmKv3cxwq6XQCgnN5BCd5puHgt8ksx76kxpPD3HsBFeKfgHJwVXlA8EoJOLzAb2arzlIM6jJctXi8NX2QA848kq6fzfW9l/JwJ6w0MHYxl2GaLsOC0rb5aOZdEac=
Message-ID: <d45b08f00706210655l1c0309f8t634c512406c57956@mail.gmail.com>
Date: Thu, 21 Jun 2007 15:55:39 +0200
From: "Emmanuel Lecharny" <elecharny@gmail.com>
Reply-To: elecharny@iktek.com
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Moving from IoHandlerChain to something easier to debug
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

in the different protocols we have in ADS, we are using a
IoHandlerChain inherited class to handle the received messages.
Although I think that this pattern is sometime usefull if you want to
use an evolving message handling (like adding dynamically some
processing), in this very case, we have just fixed handlers.

There are three main concerns whith this pattern usage :
1) it's really painfull to debug, as you have to set BP in every
handler when you step through the code
2) it slow down the processing for heavily loaded servers
3) it forces the implementor to inject data through a session
attribute, which is not exactly the best solution, but you do'nt have
any other

I would suggest to switch from this pattern to a simpler one, where we
keep the handler decomposition (I like the idea of decomposing
treatments in small disconnected methods, compared to a big fat
method), but using as many methods as we have handlers. Doing so will
remove the 2 first points, without modifying the logic of the current
code, while the 3rd point will substitute a parameter passing to a
session storage.

The last gain is that we won't have anymore 150 lines in stackTraces ...

wdyt ?

--=20
Regards,
Cordialement,
Emmanuel L=E9charny
www.iktek.com