<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Context Aware Event Processing</title>
	<atom:link href="http://rulecore.com/CEPblog/?feed=rss2&#038;p=92" rel="self" type="application/rss+xml" />
	<link>http://rulecore.com/CEPblog/?p=92</link>
	<description>Marco writes about Complex Event Processing</description>
	<lastBuildDate>Tue, 07 Sep 2010 12:41:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Marco</title>
		<link>http://rulecore.com/CEPblog/?p=92&#038;cpage=1#comment-805</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Thu, 05 Feb 2009 09:10:37 +0000</pubDate>
		<guid isPermaLink="false">http://rulecore.com/CEPblog/?p=92#comment-805</guid>
		<description>Sounds really interesting. It&#039;s nice to see what kind of different concepts are used to provide a context. I think that there will be many different approaches to context management as it needs to be handled differently depending on the concepts used in various products.

For example in ruleCore I think you could describe the approach as &quot;events that are somehow related&quot; to describe what we mean by our event stream views, which are our concept to create and maintain a context.</description>
		<content:encoded><![CDATA[<p>Sounds really interesting. It&#8217;s nice to see what kind of different concepts are used to provide a context. I think that there will be many different approaches to context management as it needs to be handled differently depending on the concepts used in various products.</p>
<p>For example in ruleCore I think you could describe the approach as &#8220;events that are somehow related&#8221; to describe what we mean by our event stream views, which are our concept to create and maintain a context.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louie Lovas</title>
		<link>http://rulecore.com/CEPblog/?p=92&#038;cpage=1#comment-801</link>
		<dc:creator>Louie Lovas</dc:creator>
		<pubDate>Thu, 05 Feb 2009 01:28:03 +0000</pubDate>
		<guid isPermaLink="false">http://rulecore.com/CEPblog/?p=92#comment-801</guid>
		<description>Very interesting topic. In Apama, we have the notion of a “sub-monitor”, which can be thought of as a separate “instance” of a set of business logic. Each sub-monitor can load and maintain its own data (e.g. consider a sub-monitor as corresponding to a different situation, with different timeouts, key indicators, client data etc) and can set up its own listeners to key into a (different or overlapping) subset of the event space. This allows us to easily model “factory” like behavior, with each sub-monitor maintaining different state and possibly listening for different (sequences of) events – but applying the same (parameterized) basic logic (including the actions to take when an event condition becomes true). We call this our micro threading or &quot;mThread&quot; architecture.

In the latest Apama release – 4.1 – we actually go further than this and introduce the notion of contexts or silos of execution which take the factory model to the next level. ”context&quot; is a reserved word in Apama 4.1 – it defines a collection of sub-monitors which can inter-operate in a protected address space, with strong semantics for inter-context communication (via event routing). It is also the unit of parallelization – allowing the same engine to spawn multiple “contexts” which key into the event flow but execute in parallel (on multi-core architectures). Contexts in Apama provide many benefits for building complex applications that can scale massively.</description>
		<content:encoded><![CDATA[<p>Very interesting topic. In Apama, we have the notion of a “sub-monitor”, which can be thought of as a separate “instance” of a set of business logic. Each sub-monitor can load and maintain its own data (e.g. consider a sub-monitor as corresponding to a different situation, with different timeouts, key indicators, client data etc) and can set up its own listeners to key into a (different or overlapping) subset of the event space. This allows us to easily model “factory” like behavior, with each sub-monitor maintaining different state and possibly listening for different (sequences of) events – but applying the same (parameterized) basic logic (including the actions to take when an event condition becomes true). We call this our micro threading or &#8220;mThread&#8221; architecture.</p>
<p>In the latest Apama release – 4.1 – we actually go further than this and introduce the notion of contexts or silos of execution which take the factory model to the next level. ”context&#8221; is a reserved word in Apama 4.1 – it defines a collection of sub-monitors which can inter-operate in a protected address space, with strong semantics for inter-context communication (via event routing). It is also the unit of parallelization – allowing the same engine to spawn multiple “contexts” which key into the event flow but execute in parallel (on multi-core architectures). Contexts in Apama provide many benefits for building complex applications that can scale massively.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco</title>
		<link>http://rulecore.com/CEPblog/?p=92&#038;cpage=1#comment-769</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Sun, 01 Feb 2009 18:11:21 +0000</pubDate>
		<guid isPermaLink="false">http://rulecore.com/CEPblog/?p=92#comment-769</guid>
		<description>James,

I suppose that reacting only on high value customers could be done in two ways. 

In the first approach we could create a semantically rich context which contains only those events which tells us something about the trucks of our most valued customers. 

The other approach is to output an event out of our event processing system into a &quot;traditional&quot; system which could do a query or evaluate a rule to find out the value of the customer. 

I think both approaches could be used depending on your specific requirement.

In ruleCore we tend to go for the first one. Creating a very expressive way of defining the semantics of the context so that we have the right events to work on to begin with.

Maybe there&#039;s a third or fourth approach too?</description>
		<content:encoded><![CDATA[<p>James,</p>
<p>I suppose that reacting only on high value customers could be done in two ways. </p>
<p>In the first approach we could create a semantically rich context which contains only those events which tells us something about the trucks of our most valued customers. </p>
<p>The other approach is to output an event out of our event processing system into a &#8220;traditional&#8221; system which could do a query or evaluate a rule to find out the value of the customer. </p>
<p>I think both approaches could be used depending on your specific requirement.</p>
<p>In ruleCore we tend to go for the first one. Creating a very expressive way of defining the semantics of the context so that we have the right events to work on to begin with.</p>
<p>Maybe there&#8217;s a third or fourth approach too?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor</title>
		<link>http://rulecore.com/CEPblog/?p=92&#038;cpage=1#comment-764</link>
		<dc:creator>James Taylor</dc:creator>
		<pubDate>Sun, 01 Feb 2009 03:51:56 +0000</pubDate>
		<guid isPermaLink="false">http://rulecore.com/CEPblog/?p=92#comment-764</guid>
		<description>Of course you would also need to make some business decisions - the example of the truck is great but any action you take is also going to depend on knowing the value of the customers whose deliveries are on the truck - a business decision.
Context+Event is great knowledge but you need to add business decision making too.

JT</description>
		<content:encoded><![CDATA[<p>Of course you would also need to make some business decisions &#8211; the example of the truck is great but any action you take is also going to depend on knowing the value of the customers whose deliveries are on the truck &#8211; a business decision.<br />
Context+Event is great knowledge but you need to add business decision making too.</p>
<p>JT</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marco</title>
		<link>http://rulecore.com/CEPblog/?p=92&#038;cpage=1#comment-691</link>
		<dc:creator>Marco</dc:creator>
		<pubDate>Wed, 21 Jan 2009 10:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://rulecore.com/CEPblog/?p=92#comment-691</guid>
		<description>Thanks for the link to the paper, I&#039;ll read it as soon as I have the patience to register on that site and go through the hassle of using my personal card to buy it ;)

Context should indeed be in the glossary. Perhaps also some note about the difference between the windows and context concepts? I tend to spend much time in explaining how a window and a context differs.</description>
		<content:encoded><![CDATA[<p>Thanks for the link to the paper, I&#8217;ll read it as soon as I have the patience to register on that site and go through the hassle of using my personal card to buy it <img src='http://rulecore.com/CEPblog/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>Context should indeed be in the glossary. Perhaps also some note about the difference between the windows and context concepts? I tend to spend much time in explaining how a window and a context differs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Opher Etzion</title>
		<link>http://rulecore.com/CEPblog/?p=92&#038;cpage=1#comment-688</link>
		<dc:creator>Opher Etzion</dc:creator>
		<pubDate>Tue, 20 Jan 2009 20:09:01 +0000</pubDate>
		<guid isPermaLink="false">http://rulecore.com/CEPblog/?p=92#comment-688</guid>
		<description>Hi Marco.  welcome to the context world.  I agree that context is a major abstraction in event processing and proposed to add it to the EPTS glossary.   We have made context as a major concept in AMiT - an abstract of a relatively old paper (from 2003) can be found here:  http://www2.computer.org/portal/web/csdl/abs/proceedings/ams/2003/1983/00/19830160abs.htm

Temporal contexts are much richer than time windows.  
Some more discussion in the notion of context from various aspects can be found here:  http://epthinking.blogspot.com/search/label/context

Have fun and hope you dress well when going outside.</description>
		<content:encoded><![CDATA[<p>Hi Marco.  welcome to the context world.  I agree that context is a major abstraction in event processing and proposed to add it to the EPTS glossary.   We have made context as a major concept in AMiT &#8211; an abstract of a relatively old paper (from 2003) can be found here:  <a href="http://www2.computer.org/portal/web/csdl/abs/proceedings/ams/2003/1983/00/19830160abs.htm" rel="nofollow">http://www2.computer.org/portal/web/csdl/abs/proceedings/ams/2003/1983/00/19830160abs.htm</a></p>
<p>Temporal contexts are much richer than time windows.<br />
Some more discussion in the notion of context from various aspects can be found here:  <a href="http://epthinking.blogspot.com/search/label/context" rel="nofollow">http://epthinking.blogspot.com/search/label/context</a></p>
<p>Have fun and hope you dress well when going outside.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
