Re: [picocontainer-dev] ThreadLocal caching - review please

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

> Jörg in particular, can people have a look at
> http:// 
>
svn.picocontainer.codehaus.org/changelog/picocontainer/?cs=3808
> 
> Its possibly too simple.  I need help to understand
> that if so.

Simple is cool. I think it is enough. 

> Its designed for web apps.  The theory is create and
> populate three  
> containers only.  One for App, one for session and
> one for request.

3 Containers only?   I use one container per directory
( for example to activate menu entries or check
security / preconditions ) 

> The Session and Request instance will cache
> components on ThreadLocal.
> After each request you'd flush the cache (todo) on
> the request container
> The web container used must be able to round-trip
> the session  
> container and its threadlocal cached comps
> perfectly.

Nanowar should be revorked for this to assure that
everything is flushed properly - threads are reused in
most app servers. 

It has also to play nice with scripting builders and 
other funny adapters - like hot swappable. 
( a lot to think about ) 
regards,

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


       
____________________________________________________________________________________Ready for the edge of your seat? 
Check out tonight's top picks on Yahoo! TV. 
http://tv.yahoo.com/

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

    http://xircles.codehaus.org/manage_email