Re: [picocontainer-dev] [IMPORTANT] caching is not on by default anymore?

--- Paul Hammant <[email protected]> wrote:


> ... the NanoContainer architecture that is dependant
> on  
> ScriptedContainer / ScriptedContainerBuilder is not
> the best way (Joe  
> kinda apologized for the IntegrationKit stuff a
> couple of years back).

This is indeed too complicated and yought to be
streamlined - but for now there is usable default.

> With Pico2, in gems there is a
> HttpSessionStoringAdapter
> 
> Also see
> http://picocontainer.org/web-frameworks.html
> 
> The intent is to provide a much more efficient way
> to store components  
> on the session.  The current NanoWar way is to
> rebuild containers per  
> session.  The new way reuses containers, but has a
> different store.

well, I will have to take a look to it, but idea seems
good.  I will see to apply this also to container
chains.

And request scope is storing on request, or in thread
locals? If thread locals, then it is dangerous.
( threads are reused in jboss )

and what is with lifecycles?


regards,

----[ Konstantin Pribluda http://www.pribluda.de ]----------------
JTec quality components: http://www.pribluda.de/projects/


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping

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

    http://xircles.codehaus.org/manage_email