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

So my feeling is that ...

On Dec 23, 2007, at 7:50 PM, Konstantin Priblouda wrote:

> Hi all,
>
> I just discovered that caching is not activated on
> default pico container by default anymore - is
> it intentional? If yes, all the nanowar stuff
> has to be checked and ensured that it is activated.
>

... 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).

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.

> Otherwise there will be a lot of fun for web-tier
> users.

Agree.


My hope is that the entire Nano container architecture gets a re- 
implementation where is appropriate for Pico2 (Composer1) codelines.   
Obviously the testcases are of high value, but the internal  
implementations that depends on ContainerBuilder can be redone - in a  
far more simple way.

Thoughts?

- Paul

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

    http://xircles.codehaus.org/manage_email