If there are multiple threads that make calls to
ReaderWriterLock.AcquireWriterLock(x), clearly all but one will be
blocked at any time.

Is the order at which the threads acquire lock (as the previous one
releases) the same order that the threads called AcquireWriterLock in
the first place (e.g. the second thread to call AcquireWriterLock will
be the second to acquire the lock, and so on, like a FIFO?)

Secondly, why isn' this in the documentation? (or did I miss it?)

Many thanks for any assistance

Tom

On 2007-11-27 22:26:39 -0800, Tom <(E-Mail Removed)> said:

> [...]
> Is the order at which the threads acquire lock (as the previous one
> releases) the same order that the threads called AcquireWriterLock in
> the first place (e.g. the second thread to call AcquireWriterLock will
> be the second to acquire the lock, and so on, like a FIFO?)
>
> Secondly, why isn' this in the documentation? (or did I miss it?)

I don't see anything that I'd call unambiguously explicit. But the
discussion in the main class page
(http://msdn2.microsoft.com/en-us/lib...riterlock.aspx)
talks about reader and writer queues, which suggests to me that it's a
FIFO operation.

I should probably install Reflector some day. I hear it's useful for
looking at this sort of implementation detail. I don't have first-hand
knowledge of it, but it seems likely you could use Reflector to get a
more reliable answer.

Pete