dotnet general: how to read status of AutoResetEvent? -- dotnet general

You're in the

dotnet general

group:

how to read status of AutoResetEvent?

RE: how to read status of AutoResetEvent?

AMercer
2/29/2008 1:15:00 PM

dotnet general:

[quoted text, click to view]

Re: how to read status of AutoResetEvent?

AMercer
2/29/2008 3:56:00 PM

[quoted text, click to view]

So, it all depends on how often the OP wants to read it's current status.
Using WaitOne less frequently than, say, once a minute should pose no
problems. Using it more than a few times a second will be a problem. I
wonder what the OP had in mind?

how to read status of AutoResetEvent?

buu
2/29/2008 7:51:49 PM

so, I have a private object as system.threading.AutoResetEvent, and I would
like to read it's current status.

currently I have an another boolean object wich I update together with an
AutoResetEvent, but I don't think it's the best practice....

Re: how to read status of AutoResetEvent?

Jeroen Mostert
2/29/2008 8:18:46 PM

[quoted text, click to view]
You can't, for a good reason: it couldn't possibly be made thread-safe.

[quoted text, click to view]
Actually, it is, but only if you use locks to make this access thread-safe.

In many cases, using a monitor is more flexible and easier to get right than
using an AutoResetEvent. You can use Monitor.Pulse() and Monitor.Wait() to
let threads notify each other in much the same way.

bool conditionMet;
object conditionMonitor = new object();

lock (conditionMonitor ) {
if (!conditionMet) Monitor.Wait(conditionMonitor);
// conditionMet == true and no other thread is in this monitor
}

....

lock (conditionMonitor) {
conditionMet = true;
Monitor.Pulse(conditionMonitor);
}

--

Re: how to read status of AutoResetEvent?

Jeroen Mostert
2/29/2008 11:54:35 PM

[quoted text, click to view]

This is a bad idea. First, it changes the state of the event if it's
signaled. You can set the event again, of course, but only if you take care
not to wait for it immediately again afterwards to "check" the status. In
the worst case you'd have to take over the responsibilities of the other
waiting threads.

Second, if the event is not signaled, waiting is likely to invoke a context
switch, which will probably take more than 1 millisecond, so this technique
doesn't scale. In fact, it's bizarrely more costly than checking a
self-maintained boolean, probably even if you factor in locking costs.

--

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages in the dotnet general group.

View Other Months
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008

home · blog · groups

Questions? Comments? Contact the dn