synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] [Assigned] (SYNAPSE-975) Non blocking Callout Mediator (Call Mediator)
Date Fri, 19 Sep 2014 03:54:34 GMT


Hiranya Jayathilaka reassigned SYNAPSE-975:

    Assignee: Isuru Udana Loku Narangoda  (was: Hiranya Jayathilaka)

Isuru, I believe you can see this through now.

> Non blocking Callout Mediator (Call Mediator)
> ---------------------------------------------
>                 Key: SYNAPSE-975
>                 URL:
>             Project: Synapse
>          Issue Type: New Feature
>            Reporter: Isuru Udana Loku Narangoda
>            Assignee: Isuru Udana Loku Narangoda
>         Attachments: SYNAPSE-975v2.patch, sample440.patch,
> One of the major drawbacks in Callout mediator is, it does not leverage the non-blocking
> 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message