You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Deepal Jayasinghe <de...@opensource.lk> on 2005/10/27 15:27:51 UTC
Synapse Architecture
Hi all;
Two Infravio guys came from India (Sathish , Vikas) and Axis2 guys had a discussion whole today and finally we came up with the following Architecture.
The synapse execution is done in three phases,
1. In-phase
2. Rule-processing
3. Out-phase
In In-phase for the mediators does not have pre-condition so they can run as a sequence , after finishing that
There can be rules that run in a loop and the loop will end depending on the mediator status or the rule pre-condition , finally the out-phase will be invoked and they can be also run in sequence without considering pre-condition.
Then the above picture can be described as follows;
step 1 : Synapse Engine get a message , then that will ask Rule Processor to calculate rule for that particular message , it will calculate in-phase mediators and give that to SynaseEngine.
step 2 : Then it will invoked those Rules (the graphical representation of rule is as picture below) , after finishing that chain , looping will start
step 3 : here the a rule will be invoked and evaluate the condition and will decide to continue or stop , after finishing the loop , we assume that RuleProcessor will be calculated the out-phase rules and
step 4 : Will be called those rules
step 5 : finally the message will be drop into the bus (if there is any)
And this picture almost based on Paul's picture , since it can be problem if we are going to use separate transports for Synapse (code duplication etc) , and we hope to discuss more on this in the IRC
comments ....
Thanks,
Deepal
................................................................
~Future is Open~
Re: Synapse Architecture
Posted by Eran Chinthaka <ch...@opensource.lk>.
Jaliya,
The second picture is an elaboration of what we need to have in Rx boxes
of the first picture. So for any rule, which passes for a particlular
message, we need to create a one way axis engine, invoke the inflow and
goes to MR and then that will call a mediation.
So please look at the two pictures in that way and they do not stand
alone seperately.
HTH.
Chinthaka
Jaliya Ekanayake wrote:
>Hi Deepal,
>
>Why we have inflow -> MR -> Mediation.
>Is it not possible to do the mediation after the transport and then use different pipelines for mediation?
>that is Transport -> Rule Engine -> Mediation
>
>Please explain.
>
>Thanks,
>
>Jaliya
>
>
>
> ----- Original Message -----
> From: ant elder
> To: synapse-dev@ws.apache.org
> Sent: Thursday, October 27, 2005 10:43 AM
> Subject: Re: Synapse Architecture
>
>
> Could how phase2 "rule-processing" works be explained a bit more?
>
> Does each loop iteration reevaluate every rule that is in phase2 regardless of if it evaluated to false on a previous iteration?
>
> What terminates the phase2 loop, is it when there is an iteration where all rules evaluate to false?
>
> If a phase2 mediator returns false does it still stop all processing - so no more phase2 and no out-phase?
>
> ...ant
>
>
> On 10/27/05, Deepal Jayasinghe <de...@opensource.lk> wrote:
> Hi all;
>
> Two Infravio guys came from India (Sathish , Vikas) and Axis2 guys had a discussion whole today and finally we came up with the following Architecture.
>
>
>
>
> The synapse execution is done in three phases,
> 1. In-phase
> 2. Rule-processing
> 3. Out-phase
>
> In In-phase for the mediators does not have pre-condition so they can run as a sequence , after finishing that
> There can be rules that run in a loop and the loop will end depending on the mediator status or the rule pre-condition , finally the out-phase will be invoked and they can be also run in sequence without considering pre-condition.
>
> Then the above picture can be described as follows;
> step 1 : Synapse Engine get a message , then that will ask Rule Processor to calculate rule for that particular message , it will calculate in-phase mediators and give that to SynaseEngine.
> step 2 : Then it will invoked those Rules (the graphical representation of rule is as picture below) , after finishing that chain , looping will start
> step 3 : here the a rule will be invoked and evaluate the condition and will decide to continue or stop , after finishing the loop , we assume that RuleProcessor will be calculated the out-phase rules and
> step 4 : Will be called those rules
> step 5 : finally the message will be drop into the bus (if there is any)
>
>
>
>
>
>
>
> And this picture almost based on Paul's picture , since it can be problem if we are going to use separate transports for Synapse (code duplication etc) , and we hope to discuss more on this in the IRC
>
>
> comments ....
>
>
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Synapse Architecture
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Deepal,
Why we have inflow -> MR -> Mediation.
Is it not possible to do the mediation after the transport and then use different pipelines for mediation?
that is Transport -> Rule Engine -> Mediation
Please explain.
Thanks,
Jaliya
----- Original Message -----
From: ant elder
To: synapse-dev@ws.apache.org
Sent: Thursday, October 27, 2005 10:43 AM
Subject: Re: Synapse Architecture
Could how phase2 "rule-processing" works be explained a bit more?
Does each loop iteration reevaluate every rule that is in phase2 regardless of if it evaluated to false on a previous iteration?
What terminates the phase2 loop, is it when there is an iteration where all rules evaluate to false?
If a phase2 mediator returns false does it still stop all processing - so no more phase2 and no out-phase?
...ant
On 10/27/05, Deepal Jayasinghe <de...@opensource.lk> wrote:
Hi all;
Two Infravio guys came from India (Sathish , Vikas) and Axis2 guys had a discussion whole today and finally we came up with the following Architecture.
The synapse execution is done in three phases,
1. In-phase
2. Rule-processing
3. Out-phase
In In-phase for the mediators does not have pre-condition so they can run as a sequence , after finishing that
There can be rules that run in a loop and the loop will end depending on the mediator status or the rule pre-condition , finally the out-phase will be invoked and they can be also run in sequence without considering pre-condition.
Then the above picture can be described as follows;
step 1 : Synapse Engine get a message , then that will ask Rule Processor to calculate rule for that particular message , it will calculate in-phase mediators and give that to SynaseEngine.
step 2 : Then it will invoked those Rules (the graphical representation of rule is as picture below) , after finishing that chain , looping will start
step 3 : here the a rule will be invoked and evaluate the condition and will decide to continue or stop , after finishing the loop , we assume that RuleProcessor will be calculated the out-phase rules and
step 4 : Will be called those rules
step 5 : finally the message will be drop into the bus (if there is any)
And this picture almost based on Paul's picture , since it can be problem if we are going to use separate transports for Synapse (code duplication etc) , and we hope to discuss more on this in the IRC
comments ....
Thanks,
Deepal
................................................................
~Future is Open~
Re: Synapse Architecture
Posted by ant elder <an...@gmail.com>.
Could how phase2 "rule-processing" works be explained a bit more?
Does each loop iteration reevaluate every rule that is in phase2 regardless
of if it evaluated to false on a previous iteration?
What terminates the phase2 loop, is it when there is an iteration where all
rules evaluate to false?
If a phase2 mediator returns false does it still stop all processing - so no
more phase2 and no out-phase?
...ant
On 10/27/05, Deepal Jayasinghe <de...@opensource.lk> wrote:
>
> Hi all;
> Two Infravio guys came from India (Sathish , Vikas) and Axis2 guys had a
> discussion whole today and finally we came up with the following
> Architecture.
> The synapse execution is done in three phases,
> 1. In-phase
> 2. Rule-processing
> 3. Out-phase
> In In-phase for the mediators does not have pre-condition so they can run
> as a sequence , after finishing that
> There can be rules that run in a loop and the loop will end depending on
> the mediator status or the rule pre-condition , finally the out-phase will
> be invoked and they can be also run in sequence without considering
> pre-condition.
> Then the above picture can be described as follows;
> step 1 : Synapse Engine get a message , then that will ask Rule Processor
> to calculate rule for that particular message , it will calculate in-phase
> mediators and give that to SynaseEngine.
> step 2 : Then it will invoked those Rules (the graphical representation
> of rule is as picture below) , after finishing that chain , looping will
> start
> step 3 : here the a rule will be invoked and evaluate the condition and
> will decide to continue or stop , after finishing the loop , we assume that
> RuleProcessor will be calculated the out-phase rules and
> step 4 : Will be called those rules
> step 5 : finally the message will be drop into the bus (if there is any)
> And this picture almost based on Paul's picture , since it can be
> problem if we are going to use separate transports for Synapse (code
> duplication etc) , and we hope to discuss more on this in the IRC
> comments ....
>
> Thanks,
> Deepal
> ................................................................
> ~Future is Open~
>