directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Trustin Lee <trus...@gmail.com>
Subject Re: [jira] Commented: (DIRMINA-121) Per-port filter chain
Date Thu, 17 Nov 2005 12:00:00 GMT
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/

Mime
View raw message