Sponsored Content
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News A Complex Event = Sum (Events) + Situational Knowledge Post 302225652 by Linux Bot on Saturday 16th of August 2008 05:20:05 AM
Old 08-16-2008
A Complex Event = Sum (Events) + Situational Knowledge

Tim Bass
08-16-2008 02:11 AM
Sometimes we read some opinions about CEP where folks*opine that*”complex event processing” is really about processing “complex events” and not about “complex” “event processing”.** The truth be told, processing “complex events” requires “complex” “event processing” so there is really no difference between the two ways of expressing CEP.

You can not process complex events in some very simple way and expect to get accurate results.* You need knowledge, represented by*one or more*situational*models, to process complex events.

Some folks, like to say that a “complex event” is simply an event which is an aggregation of two more more event objects.*** If you follow this (flawed) logic, then counting integers is complex event processing; because 1 plus 1 is 2, and 2 is an aggregation of 1 and 1, so 2 is a complex event (not!).**

Since we know that counting is not a complex processing operation, then some folks would say that you can process complex events with very simple operations because you are processing complex events , in the case adding 1 to the previous number (counting), enriching an event object.

This is simply nonsense.

The logic flaw is that the basic definition of a “complex event” (used*by many*people)*is wrong.** A complex event is not simply an event object with two more more events as sub-components.*

A complex event is when two event objects are*combined (processed)*to*form a complex object*with a*higher degree of inference, or situational knowledge.** One plus one equals more than two in complex event processing, because the combination of event objects requires knowledge (e.g. a*situational model).
A Complex Event = Sum (EventsObjects) + Situational Knowledge

Let there be no mistake about it.****Complex event processing is the complex processing of complex events.***You cannot accurately process complex events with simple*event processing models.

The simple processing of complex events is not CEP, it is simple event processing (event track-and-trace, simple event object enrichment,*simple event object aggregation, and so forth).
*



Source...
 

We Also Found This Discussion For You

1. Post Here to Contact Site Administrators and Moderators

Event Prediction - New Sports Events

Hi, Some sports predictions suggestions. Although the Celtics are still playing the Heat. Just being optimistic that they will win. Otherwise, please change to Heat. (9 Replies)
Discussion started by: ni2
9 Replies
history(n)						       Tcl Built-In Commands							history(n)

__________________________________________________________________________________________________________________________________________________

NAME
history - Manipulate the history list SYNOPSIS
history ?option? ?arg arg ...? _________________________________________________________________ DESCRIPTION
The history command performs one of several operations related to recently-executed commands recorded in a history list. Each of these recorded commands is referred to as an ``event''. When specifying an event to the history command, the following forms may be used: [1] A number: if positive, it refers to the event with that number (all events are numbered starting at 1). If the number is negative, it selects an event relative to the current event (-1 refers to the previous event, -2 to the one before that, and so on). Event 0 refers to the current event. [2] A string: selects the most recent event that matches the string. An event is considered to match the string either if the string is the same as the first characters of the event, or if the string matches the event in the sense of the string match command. The history command can take any of the following forms: history Same as history info, described below. history add command ?exec? Adds the command argument to the history list as a new event. If exec is specified (or abbreviated) then the command is also exe- cuted and its result is returned. If exec isn't specified then an empty string is returned as result. history change newValue ?event? Replaces the value recorded for an event with newValue. Event specifies the event to replace, and defaults to the current event (not event -1). This command is intended for use in commands that implement new forms of history substitution and wish to replace the current event (which invokes the substitution) with the command created through substitution. The return value is an empty string. history clear Erase the history list. The current keep limit is retained. The history event numbers are reset. history event ?event? Returns the value of the event given by event. Event defaults to -1. history info ?count? Returns a formatted string (intended for humans to read) giving the event number and contents for each of the events in the history list except the current event. If count is specified then only the most recent count events are returned. history keep ?count? This command may be used to change the size of the history list to count events. Initially, 20 events are retained in the history list. If count is not specified, the current keep limit is returned. history nextid Returns the number of the next event to be recorded in the history list. It is useful for things like printing the event number in command-line prompts. history redo ?event? Re-executes the command indicated by event and return its result. Event defaults to -1. This command results in history revision: see below for details. HISTORY REVISION
Pre-8.0 Tcl had a complex history revision mechanism. The current mechanism is more limited, and the old history operations substitute and words have been removed. (As a consolation, the clear operation was added.) The history option redo results in much simpler ``history revision''. When this option is invoked then the most recent event is modified to eliminate the history command and replace it with the result of the history command. If you want to redo an event without modifying history, then use the event operation to retrieve some event, and the add operation to add it to history and execute it. KEYWORDS
event, history, record Tcl history(n)
All times are GMT -4. The time now is 04:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy