Hi Michael, as I understand it you would have to specify a synchronized
context via a SynchronizationAttribute (the one from
System.Runtime.Remoting.Contexts NOT EnterpriseServices) and a class derived
from ContextBoundObject for there to be any difference in behaviour with
this parameter. If you are using the latter, setting it to 'true' will
prevent deadlocks by allowing other threads into the context before you gain
the WaitSleepJoin state.
It's not perfectly clear to me, though, since I've never implemented it. I
doubt many will since .NET Contexts are not terribly well documented and
their uses not well understood (I include myself in that last statement as
well).
Other than the Mutex's name being global, I don't know of any special
behaviour vis-a-vis certain naming conventions so I can't help you there.
Richard
--
C#, .NET and (a bit of) Complex Adaptive Systems:
http://blogs.geekdojo.net/Richard [quoted text, click to view] "Michael A. Covington" <look@www.covingtoninnovations.com.for.address> wrote
in message news:O9fsQec9DHA.340@tk2msftngp13.phx.gbl...
> What is the difference between
>
> myMutex.WaitOne(n,false);
>
> and
>
> myMutex.WaitOne(n,true);
>
> where n is a number of milliseconds and myMutex is a Mutex?
>
> The second parameter supposedly says whether to "exit the synchronization
> domain before waiting." What does that mean?
>
> Also, can anyone tell me anything about naming of named mutexes? I
> understand "Local\\" at the beginning of the name means something, but I
> haven't found where this is documented.
>
> Many thanks!
>
> --
>
> Michael A. Covington - Artificial Intelligence Ctr - University of Georgia
>
> "In the core C# language it is simply not possible to have an
uninitialized
> variable, a 'dangling' pointer, or an expression that indexes an array
> beyond its bounds. Whole categories of bugs that routinely plague C and
C++
> programs are thus eliminated." - A. Hejlsberg, The C# Programming
Language
>
>
