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?
Use manual reset events to trigger multiple threads off of a single event.
Here is an example which uses "Manual Reset Event" flag
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With