I started to like your suggestion, and I'd like to see its realization. :)
2005/11/15, Irving, Dave <[EMAIL PROTECTED]
>:
Good idea. Perhaps we can use session attributes here?
Sounds cool.
BTW J-F once asked us about emitting an event virtually (not a real I/O event but fabricated one). I guess we can support this in our ConnectionChain by exposing event emitting methods like I did in AbstractIoFilterChain?
Cheers,
Trustin
-- So why don't we just dispatch based on IoSession??
I.e, we have something like a "ConnectionChains" class which holds all
chains - mapped against IoSessions.
The final filter of a sub-chain (sessionManager chain, port chain,
session chain) is set by ConnectionChains to some private inner class.
When the last filter of a sub-chain is invoked, ConnectionChains does a
( O(1) ) look up for the correct ConnectionChain based on session and
delegates.
Good idea. Perhaps we can use session attributes here?
This allows us to get all the benefits previously discussed and solves
the NextFilter problem (including completely asyncronous calls to
NextFilter) without requiring cloning (which could be costly for some
filters).
How does that sound?
Sounds cool.
BTW J-F once asked us about emitting an event virtually (not a real I/O event but fabricated one). I guess we can support this in our ConnectionChain by exposing event emitting methods like I did in AbstractIoFilterChain?
Cheers,
Trustin
what we call human nature is actually human habit
--
http://gleamynode.net/
