[picocontainer-dev] While looking at the streamlining of NanoWar ...

... and given my task is to replace 'one container per session and one  
container per request' with three 'static' containers + some  
threadlocal store magic ...

... a problem is that start()/stop()/dispose() will have to be  
rethought for session and request scoped components.

Do people use lifecycle for session or request scoped components?

- I'm guessing the answer is yes, but what for ?

What if these session and request containers, did not have state  
themselves, but merely cascaded start/stop/dispose to the components  
they manage ?  i.e. StatelessPicoContainer (or better name)


- Paul

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email