I was accessing a service, not Axis-based, that used cookies to maintain session information. Libcurl could preserve cookie information across messages, which was not done at that time in the HTTP support. I've not looked at the current source to see if this has been added to the native implementation.
Bill Mitchell [email protected] From: Nandika Jayawardana [mailto:[email protected]] Sent: Monday, May 31, 2010 12:17 AM To: Apache AXIS C Developers List Subject: Re: Axis2C - HTTP transports (native vs. libcurl) The difference between libcurl and native axis2/c http transport was HTTP keep alive support availability in libcurl transport. However, now keep alive support is available in native HTTP transport as well. Therefore, AFAIK there isn't a difference using libcurl or native axis2/c transport. Regards Nandika On Mon, May 31, 2010 at 5:44 AM, Nadir Amra <[email protected]> wrote: Just trying to understand what the benefits are in using the HTTP transport based on libcurl vs. the native axis2/c HTTP transport? Basically is there something that is not supported in the native implementation? Nadir Amra Integrated Web Services for IBM i Operating System Internet: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] -- http://nandikajayawardana.blogspot.com/ WSO2 Inc: http://www.wso2.com
