Re: Rule Engine / Dispatcher

[Paul Fremantle]

If the Rule Engine is a handler that takes over control of the message then it can iterate through the rules. Each time it comes to a hit, it uses a separate (i.e. not the one that this handler is running under) AxisEngine to execute the modules and mediator for that rule. It retains control until no more rules match and then sends the message on.

Paul

On 10/18/05, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote:

On Tue, 2005-10-18 at 16:27 +0100, Paul Fremantle wrote:
> Saminda / folks
>
> I've been looking at the code you've posted. I also talked it over
> with Ant Elder. It seems one difference between my prototype code and
> yrs is that in mine the rule engine retains control.
> I think that it is possibly a more robust model. For example, if each
> rule requires a new inflow then there has to be a way for the
> dispatcher to maintain state.

I haven't looked at Saminda's code but we can do that right now even
with the execution engine being a module.

> One option that occurred to us was for Synapse to launch a new
> AxisEngine and then retain control.

I'm confused .. AxisEngine is stateless; so how does this work?

Sanjiva.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]