RE: [picocontainer-dev] Storing Cached items in HttpSession?
Jörg Schaible <[email protected]>
| Newsgroups | gmane.comp.java.picocontainer.devel |
|---|---|
| Message-ID | <[email protected]> |
+1. The Pico should pick up the deps in the session automatically without being stored itself. There's just one thing left: How will you support the lifecycle i.e. how do you know that a component has been started/stopped ... ? Paul Hammant wrote on Monday, August 13, 2007 2:50 AM: > I think so, yes. > > - Paul > > On Aug 12, 2007, at 1:41 PM, Jacob Kjome wrote: > >> >> Will this new code avoid the issue of serializing the app container >> along with the session container while still allowing the app >> container to be the session container's parent? I haven't looked >> at nanowar in quite a while, but I don't think this issue was ever >> cleanly resolved. If you put non-serializable objects in the app >> container and the session container is serialized, deserialization >> will fail because of the non-serializable objects in the app >> container. >> >> Jake >> >> At 10:09 AM 8/12/2007, you wrote: >>> >>> --- Paul Hammant <[email protected]> wrote: >>> >>>> For a session container (web app), can we store the Cached items in >>>> the HttpSession? I mean as an alternative to >>>> storing the whole >>>> container in the session ? >>> >>> session container shall be available on session anyway - >>> to construct request container. >>> >>> regards, >>> >>> ----[ Konstantin Pribluda http://www.pribluda.de ]---------------- >>> JTec quality components: http://www.pribluda.de/projects/ >>> >>> >>> >> >> _____________________________________________________________ >> ________ _ >>> ______________ >>> Looking for a deal? Find great prices on flights and hotels with >>> Yahoo! FareChase. http://farechase.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 >> > > > --------------------------------------------------------------------- > 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