Can a single SetEvent() trigger multiple WaitForSingleObject()

Question

This:

http://msdn.microsoft.com/en-us/library/ms686915(VS.85).aspx

Would seem to suggest not.

I have three processes communicating via pipes. Process A Creates an event, Process B & C each use WaitForSingleObject (in a second thread).

So now we have -TWO- Processes each waiting for a -SINGLE- event.

Process A fires the event with SetEvent(), Process B responds, process C does not.

Conclusion:

Each WaitForSingleObject() requires a unique Event... Correct?

Answer 1

Use manual reset events to trigger multiple threads off of a single event.

Here is an example which uses "Manual Reset Event" flag

Answer 2

You can use the Manual Reset Evenets and the PulseEvent function to release all of the threads currently waiting for the event.

Note however, that this approach is inherently racy, as there is no way to tell which are "the threads currently waiting ...". You should use a more reliable synchronization mechanism if exact matching of the wakeup/2 wait events are needed.