Re: mina component lifecycles

[peter royal]

On Mar 3, 2006, at 11:56 PM, Trustin Lee wrote:

On 3/4/06, peter royal <[EMAIL PROTECTED]> wrote:

        lm.add( connector );

high latency when the first session is ceated.  I thought I/O threads

very simple and light.

Interesting. For now all I/O threads start and stop automatically just like we init and destroy filters. Will this also become a problem? It may cause (acceptors, connectors and SocketIoProcessors) are OK to exclude from the managee list because we can control it very easily and destroy process is

ya, IO threads would be fine.. I typed that late last night and just threw all the components in there :)

and then, when the system is done:

        lm.dispose();

doesn't call destroy() at all, and destroy() will be invoked by

each session?

This sounds good. So the modified IoFilterLifecycleManager calls init() but BasicLifecycleManager? Then what happens to the filters instantiated for

-pete
-pete

--
[EMAIL PROTECTED] - http://fotap.org/~osi

I'd say that IoFilterLM could go away.. and take Michael's idea and wrap what the IoFilterLCM does in a decorator that can wrap IoFilter instances when people wish to have the in-use refcounting and variable occurrences of Init/Destroy.

smime.p7s
Description: S/MIME cryptographic signature