People (like me) seem to have problems in simple, straightforward scenarions. It's surprising to have container manifest such behaviour, i.e. track all components which leeds to memory leaks. If we look at disposable components in container as "advanced" stuff, requiring all tracking release policy & mandatory "manual" release of each component makes sense (i.e. instead of dispose you call container.Release)
On Wed, Mar 4, 2009 at 11:30 PM, hammett <[email protected]> wrote: > > I fail to see how to implications and side effects of not disposing an > object graph can be considered success. > > > On Wed, Mar 4, 2009 at 12:21 PM, Victor Kornov <[email protected]> wrote: > > I believe Ayende's point is to make users to fall into the pit of > success. > > > > On Wed, Mar 4, 2009 at 11:19 PM, hammett <[email protected]> wrote: > >> > >> I'm not sure misuse is a good argument to change this behavior. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
