2005/11/17, Irving, Dave <[EMAIL PROTECTED]>:

 >  I thought IoFilter.init(IoFilterchain, NextFilter, IoSession) makes sense instead.  Am I missing something? :) 
 
The only problem here is that it implies that the filter always has a session after it has been init'ed.
For shared filters this may not be the case (for example, a port filter would be init'ed at first use, but that doesn't mean it'll always have any sessions to talk to).
 
Keeping IoSession out of init (IMHO) steers implementors towards using init / destroy for per-filter initialisation (such as obtaining resources).
A filter which wants to kick out events when a session is created can use sessionCreated for this.

Is this for another implementation which doesn't copy the chain, right?

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

Reply via email to