Re: Synchronous http

["M.A. Khemila" <mk...@icloud.com>]

Thanks for clarifying! 

I think I was confused because my client was blocking when the service suspends my api. This happens when the ultimate endpoint is not available. I figured out how to handle that by adding a suspendOnFailure configuration to my address endpoint and adding an errorHandler to my inSequence.

On Sep 29, 2017, 12:41 PM, at 12:41 PM, Isuru Udana <is...@gmail.com> wrote:
>Hi,
>
>Even though synapse engine and http transport is non-blocking, that
>doesn't
>mean that client or backend server need to be aware of it. Non-blocking
>behaviour is just a nature of underlying implementation of synapse
>(behaviour of java threads). External parties don't need to worry about
>synapse implementation details. So by default synapse supports
>synchronous
>http protocol standards.
>
>Thanks.
>
>On Fri, Sep 29, 2017 at 9:43 PM, M.A. Khemila <mk...@icloud.com>
>wrote:
>
>> Hi,
>>
>> By default, synapse uses the non-blocking https. Is there a way to
>> override synapse to use blocking https.
>>
>> Basically, I have restful micro services which are meant to be used
>> synchronously. I am using a synapse api configuration which receives
>https
>> requests and forwards to the appropriate micro service based on uri
>> patterns. Because synapse uses the non-blocking https by default, the
>> clients need to be aware of this fact and behave accordingly, which
>is
>> something I want to really avoid.
>>
>> Any idea?
>>
>> Thank you!
>
>
>
>
>-- 
>*Isuru Udana*
>Senior Technical Lead
>
>
>
>
>*; WSO2 Inc.; http://wso2.com <http://wso2.com>email: isudana@gmail.com
><is...@gmail.com> blog: http://mytecheye.blogspot.com/
><http://mytecheye.blogspot.com/>*