Same here, never used it, can't find a reason to use it and if u can improve performance by removing it then what are u waiting for!
Cheers, John On 29/08/2010, at 16:34, Hadi Eskandari <[email protected]> wrote: > I personally have never used it. Can't find a scenario where I would > use it in future > but if removing it means performance, go ahead. > > On Aug 29, 9:46 am, Krzysztof Koźmic <[email protected]> > wrote: >> Hey guys. >> >> I'm looking at some more serious modifications that we could do for >> Windsor 3.0 and one thing that I'd really like to get rid of is >> IKernel.RemoveComponent (not to be confused with >> IKernel.ReleaseComponent or IWindsorContainer.Release). I'm talking >> about method that is the opposite of Register, not Resolve. >> >> The method is very flawed, not thread safe, has bugs, its usability is >> at best questionable and getting rid of it (so that I can make an >> assumption that once a component is in the container it can not >> dissappear) would enable me to get rid of lots of code and make some >> performance optimizations. >> >> So my question is - what do you think about this idea - did anyone of >> you ever really used this? If so - why and for what? >> >> feedback greatly appreciated, thanks > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" 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-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" 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-users?hl=en.
