Lines Matching full:event

9 dat_evd_dequeue \- remove the first event from the Event Dispatcher event queue
19     OUT   DAT_EVENT         *\fIevent\fR
30 Handle for an instance of the Event Dispatcher.
36 \fB\fIevent\fR\fR
39 Pointer to the Consumer-allocated structure that Provider fills with the event
46 The \fBdat_evd_dequeue()\fR function removes the first event from the Event
47 Dispatcher event queue and fills the Consumer allocated \fIevent\fR structure
48 with event data. The first element in this structure provides the type of the
49 event; the rest provides the event-type-specific parameters. The Consumer
50 should allocate an \fIevent\fR structure big enough to hold any event that the
51 Event Dispatcher can deliver.
68 \fBDAT_CONNECTION_EVENT_ESTABLISHED\fR event \fIprivate_data\fR is not defined
86 The returned event that was posted from an Event Stream guarantees Consumers
87 that all events that were posted from the same Event Stream prior to the
88 returned event were already returned to a Consumer directly through a
101 The operation was successful. An event was returned to a Consumer.
119 There are no entries on the Event Dispatcher queue.
135 No matter how many contexts attempt to dequeue from an Event Dispatcher, each
136 event is delivered exactly once. However, which Consumer receives which event
138 first event unless it is the only caller. The Provider is not obligated to
139 ensure that the caller receiving the first event executes earlier than contexts
143 Preservation of event ordering within an Event Stream is an important feature
144 of the DAT Event Model. Consumers are cautioned that overlapping or concurrent
154 control to the Consumer code. Meanwhile, a context receiving a later event
158 The Event ordering is preserved when dequeueing is serialized. Potential