[rules-users] Matching consecutive events

Wolfgang Laun wolfgang.laun at gmail.com
Tue Aug 7 13:22:25 EDT 2012


To paraphrase Robert Z., "Time is just another four letter word" ;-)

Clocks are just integers, incremented by Chronos, or some other god.
If the god is lazy, it'll run slowly; if the god is eager, it'll be
fast. You can be your own god (and use a pseudo-clock). You can start
with the Big Bang, your birthday, or with the recording time of A
Bigger Bang. You don't even need to count ticks of your time: you can
count sheep, too. The only rule you should obey is: never go back in
time.

Cheers
Wolfgang


On 07/08/2012, jpullmann <jaroslav.pullmann at fit.fraunhofer.de> wrote:
>   Wolfgang, Vincent, Edson, many thanks for your support!
>   A numeric comparison of the the event timestamps did the trick.
>
>   Now I am wondering, whether using simple arithmetic operators
>   instead of explicit (built-in) temporal operators might impact the
>   automatic life-cycle management and cleanup of timed events.
>
>   Are these rules treated equally and do the involved events automatically
>   expire (based on their temporal annotations) ?
>
>   Best regards
>    Jaroslav
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://drools.46999.n3.nabble.com/Matching-consecutive-events-tp4018980p4019039.html
> Sent from the Drools: User forum mailing list archive at Nabble.com.
> _______________________________________________
> rules-users mailing list
> rules-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/rules-users
>


More information about the rules-users mailing list