[jira] [Commented] (SYNAPSE-975) Non blocking Callout Mediator (Call Mediator)

["Hiranya Jayathilaka (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SYNAPSE-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799456#comment-13799456 ] 

Hiranya Jayathilaka commented on SYNAPSE-975:
---------------------------------------------

I've just started to review this. My first question is, why do we need another send mediator? We already have two mediators that enable sending messages out. Introducing a third option might increase the level of confusion. Is there a way to somehow unify this work with the existing callout mediator?

The issue description says that it's difficult to create chaining sequences with the existing send mediator. This used to be the case, but I think the responseSequence option introduced lately addresses this issue for a great extent. Given that, what problem does this new mediator solve?

In any case, I'd prefer to spend some time on reviewing this. Since it involves several changes to the mediation engine, we need to figure out exactly what we want to achieve with this.Hope that's ok with you Isuru.

> Non blocking Callout Mediator (Call Mediator)
> ---------------------------------------------
>
>                 Key: SYNAPSE-975
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-975
>             Project: Synapse
>          Issue Type: New Feature
>            Reporter: Isuru Udana Loku Narangoda
>            Assignee: Hiranya Jayathilaka
>         Attachments: sample440.patch, SYNAPSE-975v2.patch, synapse-configs-for-integration-tests.zip
>
>
> One of the major drawbacks in Callout mediator is, it does not leverage the non-blocking transports.
> Send mediator which leverages the non-blocking transports, does not provide a simple way to implement service chaining scenarios.
> Idea of the the Call Mediator is to solve the above two concerns.
> Call Mediator invokes the backend service in an asynchronous manner and return without waiting for the response.
> Mediation will be paused from that point.
> When response is received, mediation flow resumes from next mediator placed after the Call Mediator.
> User will experience two major features with the Mediator.
> * Service chaining scenarios will be much easier to implement.
> * Since both request and response can be handled within a single sequence, can define reusable sequences. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org