Thank You Gartner - Event Processing Conference #1 In the Books Post: 302137764

Sponsored Content

Special Forums News, Links, Events and Announcements Complex Event Processing RSS News Thank You Gartner - Event Processing Conference #1 In the Books Post 302137764 by Linux Bot on Wednesday 26th of September 2007 07:20:25 PM

09-26-2007

Registered User

Thank You Gartner - Event Processing Conference #1 In the Books

John Trigg
Tue, 25 Sep 2007 10:50:24 -0500
Between September 19th and 21st,Gartner held its first conference on Complex Event Processing and BusinessActivity Monitoring in Orlando, Florida. Some 200 people(by my estimation) came together to meet others interested in thesetechnologies, as well as see and hear presentations from a range ofGartner analysts, CEP vendors, educators and thought leaders, and mostimportantly users of CEP. The conference was bookended by impressivepresentations from Roy Schulte and Bill Gassman on Day One settingout the current state of the CEP and BAM market, and by Dr David Luckham whoclosed the conference with a thoughtful and insightful look at the future ofCEP.

We'll blog entries about different aspects of the conferenceover the coming days and weeks. But for now it is important to stress howvital the timing of this conference was and how its attendees have shown thatthe principles of CEP are beginning to take hold in a wide array of industriesand solutions. Between the 3 conference tracks organized by Gartner(Event Processing, Business Activity Monitoring and Event Processing in Bankingand Capital Markets) and the vendor sponsored sessions, we heard descriptionsof applications of CEP in a variety of scenarios ranging from algo trading toclickstream analysis to content distribution to manufacturing and many more.

Architectural presentations were also prevalent with manysound ideas being put forward on the relationship between the ever evolvingalphabet soup of CEP, BAM, SOA, EDA, BPM, OLTP, ESB and I am sure, manyothers. Bringing together an audience such as this to discuss bothpractical implementations and more theoretical research allows insight toflow around the CEP community and to understand the ramifications for when CEPis seen as more than just event feeds and event processing speeds. For true application infrastructures to be built on the principles andtechnologies of CEP, a wide understanding of how we can evolve therelationships between these disciplines will be key. And thatunderstanding will come from the continued holding of conferences such as thisone (already looking forward to next year in
New York) and interplay between the manydisciplines, vendors and consumers of these technologies.

Dr Luckham posited that CEP will become a ubiquitousinfrastructure technology in some 30 years. For that to be true -indeed for it to happen sooner - we all have a lot of work to put in ... but youcan be sure that it will be worth it.

Source...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

LEARN ABOUT DEBIAN

event::rpc::connection

Event::RPC::Connection(3pm)				User Contributed Perl Documentation			       Event::RPC::Connection(3pm)

NAME

       Event::RPC::Connection - Represents a RPC connection

SYNOPSIS

       Note: you never create instances of this class in your own code, it's only used internally by Event::RPC::Server. But you may request
       connection objects using the connection_hook of Event::RPC::Server and then having some read access on them.

	 my $connection = Event::RPC::Server::Connection->new (
	     $rpc_server, $client_socket
	 );

       As well you can get the currently active connection from your Event::RPC::Server object:

	 my $server	= Event::RPC::Server->instance;
	 my $connection = $server->get_active_connection;

DESCRIPTION

       Objects of this class represents a connection from an Event::RPC::Client to an Event::RPC::Server instance. They live inside the server and
       the whole Client/Server protocol is implemented here.

READ ONLY ATTRIBUTES

       The following attributes may be read using the corresponding get_ATTRIBUTE accessors:

       cid The connection ID of this connection. A number which is unique for this server instance.

       server
	   The Event::RPC::Server instance this connection belongs to.

       is_authenticated
	   This boolean value reflects whether the connection is authenticated resp. whether the client passed correct credentials.

       auth_user
	   This is the name of the user who was authenticated successfully for this connection.

       client_oids
	   This is a hash reference of object id's which are in use by the client of this connection. Keys are the object ids, value is always 1.
	   You can get the corresponding objects by using the

	     $connection->get_client_object($oid)

	   method.

	   Don't change anything in this hash, in particular don't delete or add entries. Event::RPC does all the necessary garbage collection
	   transparently, no need to mess with that.

AUTHORS

	 Joern Reder <joern at zyn dot de>

COPYRIGHT AND LICENSE

       Copyright (C) 2002-2006 by Joern Reder, All Rights Reserved.

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.10.1							    2008-10-25					       Event::RPC::Connection(3pm)