ACE_Event Class ReferenceA wrapper around the Win32 event locking mechanism. More...
Inheritance diagram for ACE_Event:
Detailed DescriptionA wrapper around the Win32 event locking mechanism.Portable implementation of an Event mechanism, which is native to Win32, but must be emulated on UNIX. All platforms support process-scope locking support. However, only Win32 platforms support global naming and system-scope locking support. Constructor & Destructor Documentation
Constructor that creates event.
Implicitly destroy the event variable.
Member Function Documentation
Explicitly destroy the event variable. Note that only one thread should call this method since it doesn't protect against race conditions.
Underlying handle to event.
Set the underlying handle to event. Note that this method assumes ownership of the <handle> and will close it down in <remove>. If you want the <handle> to stay open when <remove> is called make sure to call <dup> on the <handle> before closing it. You are responsible for the closing the existing <handle> before overwriting it.
Same as wait() above, but this one can be timed abstime is absolute time-of-day if if use_absolute_time is non-0, else it is relative time.
if MANUAL reset wake up all waiting threads set to signaled state else AUTO reset if no thread is waiting, set to signaled state if thread(s) are waiting, wake up one waiting thread and reset event
if MANUAL reset wakeup all waiting threads and reset event else AUTO reset wakeup one waiting thread (if present) and reset event
Set to nonsignaled state.
Member Data Documentation
The underlying handle.
Keeps track of whether <remove> has been called yet to avoid multiple <remove> calls, e.g., explicitly and implicitly in the destructor. This flag isn't protected by a lock, so make sure that you don't have multiple threads simultaneously calling <remove> on the same object, which is a bad idea anyway...
The documentation for this class was generated from the following files: Generated on Mon Sep 15 07:14:54 2008 for ACE by 1.5.5 |