if your actions don’t have side effects (as far as rules is
> concerned) then there is nothing stopping your actions from dispatching
> tasks to a worker thread pool which could then perform the actions
> concurrently.
>
>
>
> Thomas
>
>
>
> *From:* rules-users-boun...
After a rule has fired, the "fate" of this activation is
>> firmly established; rather than executing (timeconsuming i/o?) operations
>> inline, queue the collected date to a processor thread and let this one
>> crunch it.
>>
>> (I've only thought about this
Hello,
I’m working on a project that needs a high performance rules system for
processing batches of objects. Typically I’ll have a dozen or so rules, the
most complex of which will aggregate several objects based on timestamps and
specified data patterns. The objects will come in batches of a f
