Use of ReadWriterLockSlim would be best. On Thu, Oct 9, 2008 at 1:13 AM, Ayende Rahien <[EMAIL PROTECTED]> wrote: > all calls are ending up with release policy, which needs to do explicit > thread management to handle that safely. > it also serialize all calls to the container that end up resolving an > instance of an object. > > I change the hashtable syncronization in the all component release policy to > use RWL, but it still requires some thought > > On Tue, Oct 7, 2008 at 2:17 AM, hammett <[EMAIL PROTECTED]> wrote: >> >> Still need to do some clean up, enable some more tests. Bleeding-edge >> runners, please give windsor/mk a more careful evaluation. It might >> misbehave. If it does, please report it asap. >> Thanks >> >> -- >> Cheers, >> hammett >> http://hammett.castleproject.org/ >> >> > > > > >
-- Cheers, hammett http://hammett.castleproject.org/ --~--~---------~--~----~------------~-------~--~----~ 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 castle-project-devel@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
