Re: [Dev] [API-M] Why do we give the option of selecting transports in the gateway?

Fixed this issue for API Manager 1.8.0. Thanks, sanjeewa. On Thu, Nov 20, 2014 at 9:18 AM, Sanjeewa Malalgoda sanje...@wso2.com wrote: When we introduced multi tenancy for API Manager 1.4.0 it was working fine with NHTTP only. For users who didn't have multi tenant use case we recommend pass

[Dev] [API-M] Why do we give the option of selecting transports in the gateway?

We have the option of using NHTTP or PTT When should I use which one? What are the pros and cons? Thanks, Samisa... Samisa Abeysinghe Vice President Delivery WSO2 Inc. http://wso2.com ___ Dev mailing list Dev@wso2.org

Re: [Dev] [API-M] Why do we give the option of selecting transports in the gateway?

I guess you are referring to the commented out nhttp transports in the axis2.xml. Actually there is no usecase as such for these transports. Nhttp was left behind in commented out mode since PT was quite new in terms of maturity. And in the early days of PT, when people came across issues related

Re: [Dev] [API-M] Why do we give the option of selecting transports in the gateway?

Then we need to remove from tuning docs too... Thanks, Samisa... Samisa Abeysinghe Vice President Delivery WSO2 Inc. http://wso2.com On Wed, Nov 19, 2014 at 5:33 PM, Nuwan Dias nuw...@wso2.com wrote: I guess you are referring to the commented out nhttp transports in the axis2.xml.

Re: [Dev] [API-M] Why do we give the option of selecting transports in the gateway?

When we introduced multi tenancy for API Manager 1.4.0 it was working fine with NHTTP only. For users who didn't have multi tenant use case we recommend pass through. That is how both axis2.xml files came to product. Since now pass through is mature enough we may retire Nhttp. Thanks, sanjeewa.