+1 On Wed, Nov 19, 2014 at 11:27 AM, Kasun Indrasiri <[email protected]> wrote:
> Hi, > > At the moment 'Call' mediator offers a blocking messaging behavior on top > of non-blocking architecture (i.e. - Request and responses are handled in > different threads). However, there are requirements where we need to > support pure blocking messaging such as JMS transaction scenarios (which we > use Callout mediator at the moment). However, having 'Call' and 'Callout' > mediators is very confusing for the users and we need to have a single > mediator with both capabilities. Hence we can add the blocking support as > part of the Call mediator and deprecate Callout mediator. > > Thanks, > > > -- > Kasun Indrasiri > Software Architect > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > cell: +94 77 556 5206 > Blog : http://kasunpanorama.blogspot.com/ > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- ============================ Srinath Perera, Ph.D. http://people.apache.org/~hemapani/ http://srinathsview.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
