Re: [picocontainer-dev] Threaded Caching

In the fine grained session/request scopes start/stop are not so  
applicable and seldom used.  Meaning mostly application scoped things  
are startable.

Even so...

If a container could remember that is was started and start() each  
new session/request component that is being sought with getComponent 
(..) then it would be cool.

Ditto for requests ending and sessions ending.

We might have to push the state model from DPC into the Caching  
behavior impl(s).

- Paul

On Aug 10, 2007, at 7:59 AM, Konstantin Priblouda wrote:

>
> --- Paul Hammant <[email protected]> wrote:
>
>> It would be nice to have a second implementation of
>> Caching/Cached
>> that leverages ThreadContext to store the cached
>> components.
>>
>> Scoped containers for application, session, and
>> request are nice. It
>> might be nicer still if there were only one
>> container for all
>> sessions and requests?
>
> this could be really cool for web apps - limited
> number of containers are always in place and
> dependency resolution information remains shared ( as
> well as constants )
>
> but we shall think about stopping such container -
> it will be kind of different with vanilla one.
>
> regards,
>
>
>
> ----[ Konstantin Pribluda http://www.pribluda.de ]----------------
> JTec quality components: http://www.pribluda.de/projects/
>
>
>
> ______________________________________________________________________ 
> ______________
> Moody friends. Drama queens. Your life? Nope! - their life, your  
> story. Play Sims Stories at Yahoo! Games.
> http://sims.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe from this list please visit:
>
>     http://xircles.codehaus.org/manage_email
>


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

    http://xircles.codehaus.org/manage_email