Yeast: a general purpose event-action system
ABSTRACT Distributed networks of personal workstations are becoming the
dominant computing environment for software development organizations.
Many cooperative activities that are carried out in such environments
are particularly well suited for automated support. Taking the point of
view that such activities are modeled most naturally as the occurrence
of events requiring actions to be performed, we developed a system
called Yeast (Yet another Event Action Specification Tool). Yeast is a
client server system in which distributed clients register event action
specifications with a centralized server, which performs event detection
and specification management. Each specification submitted by a client
defines a pattern of events that is of interest to the client's
application plus an action that is to be executed in response to an
occurrence of the event pattern; the server triggers the action of a
specification once it has detected an occurrence of the associated event
pattern. Yeast provides a global space of events that is visible to and
shared by all users. In particular, events generated by one user can
trigger specifications registered by another user. Higher level
applications are built as collections of Yeast specifications. We use
Yeast on a daily basis for a variety of applications, from deadline
notification to software process automation. The paper presents an in
depth description of Yeast and an example application of Yeast, in which
Yeast specifications are used to automate a software distribution
process involving several interdependent software tools
- SourceAvailable from: Annika Hinze[Show abstract] [Hide abstract]
ABSTRACT: Today's mobile devices allow end users to get information related to particular domain based on their current location, such as the fastest route to the nearest drugstore. However, in such Location-Based Services (LBS), richer and more targeted information is desirable. In many applications, end users would like to be notified about relevant events or places to visit in the near future according to their profile. Last but not least, they do not wish to get the same information many times unless they explicitly asked for it.
Technical Report: Alerting Services in a Digital Library Environment[Show abstract] [Hide abstract]
ABSTRACT: The classical paradigm of finding information in the WWW by initiating retrieval and browsing becomes more and more ineffective. Other techniques have to be considered. Automatic delivery of contents to the user according to their needs and filtered by her profile of interests is required. Current implementations of such Alerting Services at content providers side have several drawbacks. In my research project I evaluate methods and techniques for Alerting Services with special respect to the area of digital libraries. I intend to provide a framework that supports design decisions in building alerting services depending on the infrastructure and desired system parameters. 1 Introduction Imagine one morning you just arrive at your office and switch on your computer to have a look at the recent news in your special field of research. Little pictures for each topic tell you that some interesting documents arrived. Behind one icon you find for instance the new announcements for c...
- [Show abstract] [Hide abstract]
ABSTRACT: this paper we identify the event-based style variations introduced by a number of event-based middleware infrastructures and point out the advantages and drawbacks of the different approaches as well as the open issues.