[ 
https://issues.apache.org/jira/browse/AXIS2C-861?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bill Mitchell updated AXIS2C-861:
---------------------------------

    Attachment: libcurl.diff

I am attaching a new libcurl.diff patch that merges all the changes for this 
issue and AXIS2C-830 with the changes already made to add http header support 
in AXIS2C-828.  This involved separating the release of read headers, which 
needs to happen on every request, from the release of the axis2_libcurl 
structure, that now persists throughout the session.  

If there are no objections, I will go ahead and commit these as soon as I 
finish resolving my svn setup/infrastructure issues.

> Enable client session management through http cookies in libcurl
> ----------------------------------------------------------------
>
>                 Key: AXIS2C-861
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-861
>             Project: Axis2-C
>          Issue Type: Improvement
>          Components: transport/http
>    Affects Versions: Current (Nightly)
>         Environment: Windows XP, Visual Studio 2005, libxml, libcurl
>            Reporter: Bill Mitchell
>         Attachments: libcurl.diff
>
>
> Many existing SOAP services maintain session context through HTTP cookies.  
> This can be seen in the prevalence of some mechanism to enable client cookies 
> in various SOAP stacks, including the Axis versions in Java and C++.  Without 
> re-implementing all of this in the Axis2C http transport, it would be easy 
> and convenient to provide this support for Axis2C clients built with libcurl. 
>  Libcurl already provides the underlying cookie support, all that is needed 
> is some mechanism to enable/disable this support with, say, the defined but 
> unused maintain_session option.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to