Original Survey on Event Processing Languages

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Original Survey on Event Processing Languages
# 1  
Old 11-19-2007
Original Survey on Event Processing Languages

Tim Bass
Mon, 19 Nov 2007 09:59:49 +0000
A few of us have been discussing*event processing languages (EPLs)*for a number of years, advocating*that SQL-like languages are appropriate for certain classes of CEP/EP problems, but not all.
Some*readers might recall that I published a draft survey on EPLs*to the Yahoo! CEP*Interest*group titled, (DRAFT) A Survey of Event Processing Languages (EPLs), October 15, 2006 (version 14).
A number of us CEP “grey beards” have consistently advocated that there are EPLs and analytics that are optimal for certain classes of event processing problems (and, in turn, there also are EPLs that are suboptimal for certain classes of event processing problems).
For readers who do not frequent the Yahoo! CEP group,*below here is*a link to a*copy of the original survey.



Source...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
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.11 16 Jul 2004 dat_evd_post_se(3DAT)