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

Isuru Udana Loku Narangoda commented on SYNAPSE-975:
----------------------------------------------------

I am making some changes to the logic that decide whether to enable/disable 
stack operations.
I will submit a new patch next weekend with those modifications.
                
> 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-975.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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to