Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

event(3) [php man page]

EVENT(3)								 1								  EVENT(3)

The Event class

INTRODUCTION
Event class represents and event firing on a file descriptor being ready to read from or write to; a file descriptor becoming ready to read from or write to(edge-triggered I/O only); a timeout expiring; a signal occuring; a user-triggered event. Every event is associated with EventBase . However, event will never fire until it is added (via Event::add ). An added event remains in pending state until the registered event occurs, thus turning it to active state. To handle events user may register a callback which is called when event becomes active. If event is configured persistent , it remains pending. If it is not persistent, it stops being pending when it's callback runs. Event::del method deletes event, thus making it non-pending. By means of Event::add method it could be added again. CLASS SYNOPSIS
Event final Event Constants o const integer$Event::ET32 o const integer$Event::PERSIST16 o const integer$Event::READ2 o const integer$Event::WRITE4 o const integer$Event::SIGNAL8 o const integer$Event::TIMEOUT1 Properties o publicreadonly bool$pending Methods o public bool Event::add ([double $timeout]) o public bool Event::addSignal ([double $timeout]) o public bool Event::addTimer ([double $timeout]) o public Event::__construct (EventBase $base, mixed $fd, int $what, callable $cb, [mixed $arg = NULL]) o public bool Event::del (void ) o public bool Event::delSignal (void ) o public bool Event::delTimer (void ) o public void Event::free (void ) o publicstatic array Event::getSupportedMethods (void ) o public bool Event::pending (int $flags) o public bool Event::set (EventBase $base, mixed $fd, [int $what], [callable $cb], [mixed $arg]) o public bool Event::setPriority (int $priority) o public bool Event::setTimer (EventBase $base, callable $cb, [mixed $arg]) o publicstatic Event Event::signal (EventBase $base, int $signum, callable $cb, [mixed $arg]) o publicstatic Event Event::timer (EventBase $base, callable $cb, [mixed $arg]) PROPERTIES
o $pending - Whether event is pending. See About event persistence . PREDEFINED CONSTANTS
o Event::ET - Indicates that the event should be edge-triggered, if the underlying event base backend supports edge-triggered events. This affects the semantics of Event::READ and Event::WRITE . o Event::PERSIST - Indicates that the event is persistent. See About event persistence . o Event::READ - This flag indicates an event that becomes active when the provided file descriptor(usually a stream resource, or socket) is ready for reading. o Event::WRITE - This flag indicates an event that becomes active when the provided file descriptor(usually a stream resource, or socket) is ready for reading. o Event::SIGNAL - Used to implement signal detection. See "Constructing signal events" below. o Event::TIMEOUT - This flag indicates an event that becomes active after a timeout elapses. The Event::TIMEOUT flag is ignored when constructing an event: one can either set a timeout when event is added , or not. It is set in the $what argument to the callback function when a timeout has occurred. PHP Documentation Group EVENT(3)

Check Out this Related Man Page

dat_evd_post_se(3DAT)				     Direct Access Transport Library Functions				     dat_evd_post_se(3DAT)

NAME
dat_evd_post_se - post Software event to the Event Dispatcher event queue SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_evd_post_se( IN DAT_EVD_HANDLE evd_handle, IN const DAT_EVENT *event ) PARAMETERS
evd_handle Handle for an instance of the Event Dispatcher event A pointer to a Consumer created Software Event. DESCRIPTION
The dat_evd_post_se() function posts Software events to the Event Dispatcher event queue. This is analogous to event arrival on the Event Dispatcher software Event Stream. The event that the Consumer provides adheres to the event format as defined in <dat.h>. The first element in the event provides the type of the event (DAT_EVENT_TYPE_SOFTWARE); the rest provide the event-type-specific parameters. These parame- ters are opaque to a Provider. Allocation and release of the memory referenced by the event pointer in a software event are the Consumer's responsibility. There is no ordering between events from different Event Streams. All the synchronization issues between multiple Consumer contexts trying to post events to an Event Dispatcher instance simultaneously are left to a Consumer. If the event queue is full, the operation is completed unsuccessfully and returns DAT_QUEUE_FULL. The event is not queued. The queue over- flow condition does takes place and, therefore, the asynchronous Event Dispatcher is not effected. RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE The evd_handle parameter is invalid. DAT_INVALID_PARAMETER The event parameter is invalid. DAT_QUEUE_FULL The Event Dispatcher queue is full. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.10 16 Jul 2004 dat_evd_post_se(3DAT)
Man Page