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
 64.233.184.197 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=nLhRWLb5nHyO0FPhJSCcFcyRbhxZw3WKPsA2oRgUeAlwkyXKMjetoBpav1hWOVJsVxbEQScIs+lmqyvuflwIXKCZzhujslYAjQf5m8qc79ADHAIMUBZAZiFafxxIMspwB/shRlvn72VramDz1p2kRITH7HMjrRAagOKBtOLvR7g=
Message-ID: <768dcb2e0511170400v4b926198i@mail.gmail.com>
Date: Thu, 17 Nov 2005 21:00:00 +0900
From: Trustin Lee <trustin@gmail.com>
To: Apache Directory Developers List <dev@directory.apache.org>
Subject: Re: [jira] Commented: (DIRMINA-121) Per-port filter chain
In-Reply-To: <EA9D95F907E2924A9A32F274114BCDEF806712@perth.Cellectivity.local>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_32385_16510777.1132228800592"
References: <EA9D95F907E2924A9A32F274114BCDEF806712@perth.Cellectivity.local>

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

2005/11/17, Jose Alberto Fernandez <jalberto@cellectivity.com>:
>
> Ok, can someone explain to me, how can a filter propagate an event
> asynchronously (I presume to all the sessions using it) without knowing
> what those sessions are? How can a filter make one call in its cached
> NextFilter and the message be received by ALL the sessions sharing that
> chain?


Request-response timeout filter is a good example.

It is a filter that fires exceptionCaught() event if a response for a
request message is not received for certain period. We'll have to invoke
nextFilter.exceptionCaught(). Of course, nextFilter instance should be
stored per session as you pointed out. But I don't think we need
getNextFilter() method in IoSession; it looks weird.

Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/

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

2005/11/17, Jose Alberto Fernandez &lt;<a href=3D"mailto:jalberto@cellectiv=
ity.com">jalberto@cellectivity.com</a>&gt;:<div><span class=3D"gmail_quote"=
></span><blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid r=
gb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ok, can someone explain to me, how can a filter propagate an event<br>async=
hronously (I presume to all the sessions using it) without knowing<br>what =
those sessions are? How can a filter make one call in its cached<br>NextFil=
ter and the message be received by ALL the sessions sharing that
<br>chain?</blockquote><div><br>Request-response timeout filter is a good e=
xample.<br><br>It is a filter that fires exceptionCaught() event if a respo=
nse for a request message is not received for certain period.&nbsp; We'll h=
ave to invoke=20
nextFilter.exceptionCaught().&nbsp; Of course, nextFilter instance should b=
e stored per session as you pointed out.&nbsp; But I don't think we need ge=
tNextFilter() method in IoSession; it looks weird.<br></div></div><br>Trust=
in<br>
-- <br>what we call human nature is actually human habit<br>--<br><a href=
=3D"http://gleamynode.net/">http://gleamynode.net/</a>

------=_Part_32385_16510777.1132228800592--