Re: [rules-users] Future events
You shouldn't base a streamed CEP application on time stamps dealt out
by various systems with clocks that aren't properly synchronized using
NTP or whatever. If your data doesn't conform to the very reasonable
premises of some system, your application will have to handle that.
(You can't tell the engineer to start the train just because your
clock is fast, right?)
window:time is based on the notion of CEP in real time, and the clock
of the machine running the engine reads, by definition, true Time. But
you can run the engine in cloud mode and reason over arbitrary
intervals, e.g., by inserting Inverval facts. True, you won't have
window:x any more, but from/accumulate and from/collect should
suffice.
-W
On 14/03/2012, lexsoto <lexsoto(a)gmail.com> wrote:
Well, yes that is how the engine works. But should it work this way?
Why
fire the rule if not in the appropriate time window? This still looks wrong
to me, as the intention of the rule is not observed. On the per hand, the
engine does queue events in other scenarios, so it seems arbritrary. Too
bad because this would be a ver nice way to model scheduled events using the
temporal operators.
Thanks Edson
--
View this message in context:
http://drools.46999.n3.nabble.com/Future-events-tp3826236p3827065.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users