One way that might be implemented is via a single dedicated fact type (call it Horloge) with a single field (temps). Then you could write all sorts of relations with the times in your facts. In order to work in the context of rete, Horloge's temps would have to be updated according to the progress of time - but how big do you want your chronons to be? Right, this could be made configurable. But how will this scale? Data structures keeping a large number of integers in partially sorted order are available, but Rete works differently.

Assuming that all your time-dependent facts implement a specific interface, and given Drools' WM event listener, it's easy to implement a solution for timeouts that does not require periodic polling.

-W


On 9 May 2011 20:37, kkelleyjr <karl.kelley.jr@gmail.com> wrote:
So, from all of the reading and what you have told me, this is no way
currently to do evaluations of time with the session clock on the LHS...

That statement being true: Is there any desire or plan to do evaluations of
time with the session clock on the LHS (aka the condition)?

I think it would be useful, because all processing to gather facts could be
based on cron rules... then there is no need to write cron jobs for those
processes...

Is that a bad idea?

--
View this message in context: http://drools.46999.n3.nabble.com/rules-users-Firing-the-rule-at-the-basis-of-time-tp2889494p2919950.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users