|
|
Sponsored Content
Special Forums
News, Links, Events and Announcements
Complex Event Processing RSS News
DEBS08(4) - Event-based Middleware
Post 302212413 by Linux Bot on Monday 7th of July 2008 01:00:03 PM
07-07-2008
DEBS08(4) - Event-based Middleware
vincent
Mon, 07 Jul 2008 12:26:30 +0000
Continuing on with the Distributed Event Based Systems conference, its quite surprising that the presentations on event transmission (aka intelligent middleware, content-based pub-sub, clustering pub-sub nodes for performance, secure pub-sub etc etc) and of event processing (CEP, ESP, Bayes/rules/uncertainty/queries etc etc) are not in different “streams”, given they have different audiences. From a CEP perspective, middleware is certainly necessary (and for TIBCO, er, pretty relevant), but our interest is more on what to do with events, not worry about how they arrive.
Having said that, there is clearly a connection between “intelligent / optimal distribution of events” and “distributed (complex) event processing”. And “dynamic routing” implies “intelligent nodes” that are, in effect, limited event processing agents. So the concepts are connected, although the R&D goals may, today, differ (e.g. middleware: routing resilience, performance and scaleability; CEP: event processing scaleability, performance and resilience…).
A few observations were:
Source...
Mon, 07 Jul 2008 12:26:30 +0000
Continuing on with the Distributed Event Based Systems conference, its quite surprising that the presentations on event transmission (aka intelligent middleware, content-based pub-sub, clustering pub-sub nodes for performance, secure pub-sub etc etc) and of event processing (CEP, ESP, Bayes/rules/uncertainty/queries etc etc) are not in different “streams”, given they have different audiences. From a CEP perspective, middleware is certainly necessary (and for TIBCO, er, pretty relevant), but our interest is more on what to do with events, not worry about how they arrive.
Having said that, there is clearly a connection between “intelligent / optimal distribution of events” and “distributed (complex) event processing”. And “dynamic routing” implies “intelligent nodes” that are, in effect, limited event processing agents. So the concepts are connected, although the R&D goals may, today, differ (e.g. middleware: routing resilience, performance and scaleability; CEP: event processing scaleability, performance and resilience…).
A few observations were:
- In a presentation on gaming events, the definition of Event included an “obsolete” attribute, used to indicate an event whose existance is made “irrelevant” by some subsequent event(s). I’m not sure this is a generic attribute of all events, though - the event still happened, and could be correlated (for example to identify the speed at which such events become obscolete). So this is probably useful in some contexts, and not others.
- An event metamodel was presented by the University of Waterloo in Canada, which was much more comprehensive (/complex) that the definition we use in TIBCO BusinessEvents (for Event Processing). But their goal, to make “event” a first class entity, is shared by the OMG EMP team, with whom the Waterloo group should probably be collaborating.
Source...
|
|
We Also Found This Discussion For You
1. News, Links, Events and Announcements
This Sunday, June the 7th, players in attendance will be given unique items engraved with their name. The items can be used to generate free in-game currency on a daily basis, which is particularly notable because the game's currency is bitcoin. I can't post a link yet; if you're interested, engage... (0 Replies)
Discussion started by: danielpbarron
0 Replies
LEARN ABOUT DEBIAN
yaz-url
YAZ-URL(1) Commands YAZ-URL(1) NAME
yaz-url - YAZ URL fetch utility SYNOPSIS
yaz-url [-H name:value] [-m method] [-O fname] [-p fname] [-u user/password] [-x proxy] [url...] DESCRIPTION
yaz-url is utility to get web content. It is very limited in functionality compared to programs such as curl, wget. The options must be precede the URL given on the command line to take effect. Fetched HTTP content is written to stdout, unless option -O is given. OPTIONS
-H name:value Specifies HTTP header content with name and value. This option can be given multiple times (for different names, of course). -m method Specifies the HTTP method to be used for the next URL. Default is method "GET". However, option -p sets it to "POST". -O fname Sets output filename for HTTP content. -p fname Sets a file to be POSTed in the folloing URL. -u user/password Specifies a user and a password to be uesd in HTTP basic authentication in the following URL fetch. The user and password must be separated by a slash (this it is not possible to specify a user with a slash in it). -x proxy Specifies a proxy to be used for URL fetch. SEE ALSO
yaz(7) YAZ 4.2.30 04/16/2012 YAZ-URL(1)