> From: Irving, Dave [mailto:[EMAIL PROTECTED] > > IoFilter.init(IoFilterChain parent, NextFilter nextFilter) does make > sense if you want your init to fire an event. > Filters would never be inited until a session comes along. > My proposal does have a problem though: A shared (acceptor / port) > filter would only be inited / destroyed once (not per session) because > it's the NextFilter that contains the smarts (not the filter). > It means that per session init / destroy logic should come in > "sessionCreated" / "sessionDestroyed" and not "init". > "init" / "destroy" would be used for initialisation / tear-down of the > filter itself (e.g. acquiring / releasing resources). >
So, why would we need NextFilter on the init() call? You can only use it on the sessionCreated() call, and you get it there already. Jose Alberto
