HI Natasha, Currently carbon transport sender operates in fully asynchronous nature with callbacks. what can we do is writing a callback listener which operates as a Java future and blocks the calling thread until results are available.we will look for implement an API for blocking calls for transport sender and this is required by ESB as well.
On Tue, Jun 7, 2016 at 12:35 PM, Natasha Wijesekara <[email protected]> wrote: > Hi, > > With regards to the $subject, in BPS currently we are using the HTTP > Client for external invocations as we need to do blocking HTTP calls to > invoke partner services. In C5, what are the options available to do > blocking HTTP calls ? It seems that netty transport is only supporting > non-blocking HTTP calls. > > > Best Regards, > *Natasha Wijesekare* > > *Software Engineering Intern, WSO2 Inc: http://wso2.com > <http://wso2.com/>* > *email : [email protected] <[email protected]>* > *mobile: +94 771358651 <%2B94%20771358651>* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Best Regards Isuru Ranawaka M: +94714629880 Blog : http://isurur.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
