Applied. Thanks

On Tue, Dec 30, 2008 at 11:02 PM, hammett <[email protected]> wrote:
> Yep, looks good now. Thanks
>
> On Tue, Dec 30, 2008 at 9:37 PM, Staxxx <[email protected]> wrote:
>> Hello,
>> Here's another revision of the Silverlight patch.
>> The only thing I mimicked about the MEF version is leveraging the Microsoft
>> System.Threading.ReaderWriterLockSlim under the hood in the full framework
>> version...
>> The way it's being used in the dynamic proxy required the 'upgrade from
>> reader to writer' scenario. When we call EnterReadLock/ExitReadLock on the
>> full framework it's actually
>> calling EnterUpgradeableReadLock/ExitUpgradeableReadLock so the
>> subsequent EnterWriteLock/ExitWriteLock wouldn't fail with an exception.
>> If this isn't going to work, would you mind coaching me a little more on
>> what specifically isn't correct? I'd like to attempt to write some unit
>> tests around any scenarios this thing may need to specifically support.
>> Thanks,
>> Jason
>> On Tue, Dec 30, 2008 at 3:58 PM, hammett <[email protected]> wrote:
>>>
>>> The SlimReaderWriterLock still wrong. Check MEF's codebase please.
>>>
>>>
>>> On Sun, Dec 28, 2008 at 9:07 PM, Staxxx <[email protected]> wrote:
>>> > Hello,
>>> > Let me know how this patch looks...
>>> > FYI: double check the SlimReaderWriterLock as I'm not completely
>>> > comfortable
>>> > with that...
>>> > Thanks,
>>> > Jason
>>> > >
>>> >
>>>
>>>
>>>
>>> --
>>> Cheers,
>>> hammett
>>> http://hammett.castleproject.org/
>>>
>>>
>>
>>
>> >>
>>
>
>
>
> --
> 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 [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
-~----------~----~----~----~------~----~------~--~---

Reply via email to