High-Level Constructs in the READY Event Notification System (1998)  by Robert E. Gruber, Balachander Krishnamurthy, Euthimios Panagos

From the Introduciton:

There is growing interest in the use of general-purpose event notification services as “middleware” for gluing together independently-developed distributed applications. This approach was first discussed by Oki et.al.in 1993 [14], where an early version of the (now) TIBCO Information Bus [20] was described. Since then, many other commercial products have been developed that accept events from event suppliers (publishers) and deliver them to event consumers (subscribers).  Publish-subscribe mechanisms have also been retro-fitted to existing middleware products, including persistent message queue products and TP monitors. There is also standards work in this area, including the CORBAEvent Service [15] and more recently the CORBANotification Service [16], a feature-enriched version of the Event Service.

Despite all of these products and the standardization efforts, and despite the fact that event-driven computation is not a new idea, there has been relatively little work on high level constructs for event services. The most basic event service has four kinds of entities (supplier, consumer, event, event service) and three basic functions (supply an event to the service, register interest in a kind of event, unregister interest). Existing commercial event services do not provide event models that are much richer than this most basic service. For example, there are typically no constructs that enable operations over multiple entities.
This paper describes high-level constructs (operating over multiple events, multiple consumers, etc.) provided by READY, an event notification system being developed at AT&T Labs [7]. - goto
originally Posted to cep.weblogger.com by David Soul on 2/18/04; 12:40:31 AM in the CEP section