Same Resource, Same Lock or else locking won't give you the protection you need

re: Same Resource, Same Lock or else locking won't give you the protection you need

Dean Harding — Thu, 23 Mar 2006 07:50:06 GMT

Your T3 isn't going to compile because you can't access a non-static member from a static method.

And your T5 makes too much use of the 'static' keyword as well... DoSomething wouldn't have access to non-static myLock (though DoSomethingElse would have access to static myOtherLock)

But yeah, your point is still valid :-)

re: Same Resource, Same Lock or else locking won't give you the protection you need

ricom — Thu, 23 Mar 2006 11:41:53 GMT

Yes, in fact none of the methods should be static... that's what I get for cutting and pasting too much. I'll go ahead and change them all.

re: Same Resource, Same Lock or else locking won't give you the protection you need

Norman Diamond — Sat, 25 Mar 2006 02:42:15 GMT

> that's what I get for cutting and pasting
> too much

But you did cutting and pasting in order to improve your performance in editing this blog. Remember, if the results don't have to be correct, you can do it incredibly quickly ^u^

re: Same Resource, Same Lock or else locking won't give you the protection you need

ricom — Sat, 25 Mar 2006 04:02:42 GMT

LOL, thanks :)

Locking -- Isolation -- Unit of Work -- Performance -- Solution

Rico Mariani's Performance Tidbits — Thu, 27 Apr 2006 09:12:42 GMT

A few days ago I posted a concurrency problem for commentary and I got a very nice set of responses...

Lock-uri in .NET (exemple C#) - de la Rico Mariani « .. ??i s?? nu uit s?? aleg un titlu. Ce trebuia s?? nu uit?!

Mon, 13 Aug 2007 03:54:31 GMT

PingBack from http://andreir.wordpress.com/2007/08/13/lock-uri-in-net-exemple-c-de-la-rico-mariani/