axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <sam...@wso2.com>
Subject Re: [Axis2] Added axis2_http_client
Date Mon, 09 Jan 2006 04:28:49 GMT
Sahan Gamage wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Samisa Abeysinghe wrote:
>
>  
>
>>The original idea was to have an abstraction layer on top of which
>>any desired transport lib could be used I think it would be good to
>>have libcurl support, however, we have to ensure that we have the
>>abstraction layer in place as we have done for the parser.
>>
>>Thanks, Samisa...
>>
>>Davanum Srinivas wrote:
>>
>>    
>>
>>>+1 from me.
>>>
>>>On 1/8/06, Sahan Gamage <sahan@wso2.com> wrote:
>>>
>>>
>>>      
>>>
>
>  
>
>>Davanum Srinivas wrote:
>>
>>
>>
>>    
>>
>>>>>>Reason for bringing it up is that we went thru the same
>>>>>>problems in Axis2/Java and finally settled down on Jakarta
>>>>>>Commons HTTPClient. It's real easy to get something trivial
>>>>>>working and then it goes complicated quickly (GZip streams?
>>>>>>SSL? NTLM?)...
>>>>>>
>>>>>>thanks -- dims
>>>>>>
>>>>>>On 1/8/06, Sahan Gamage <sahan@wso2.com> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>            
>>>>>>
>>>>>>>Davanum Srinivas wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>>>Sahan,
>>>>>>>>
>>>>>>>>Did anyone look for alternatives? say libcurl?
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>>>(http://curl.haxx.se/libcurl/)
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>>>thanks, dims
>>>>>>>>
>>>>>>>>On 1/8/06, Sahan Gamage <sahan@wso2.com> wrote:
>>>>>>>>
>>>>>>>>Hi,
>>>>>>>>
>>>>>>>>I have created axis2_http_client.h and
>>>>>>>>axis2_http_client.c to implement the HTTP client
>>>>>>>>functionality. Even though it can handle simple
>>>>>>>>request/response scenarios, lot of improvemnts have to
>>>>>>>>be done to handle complex cases (redirection,
>>>>>>>>100-continues). Pls review and commit the initial
>>>>>>>>version.
>>>>>>>>
>>>>>>>>- Sahan
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>>>Hi Dims,
>>>>>>>
>>>>>>>Thanks for the link. I will look at it.
>>>>>>>
>>>>>>>- Sahan
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>>>-- Davanum Srinivas : http://wso2.com/blogs/
>>>>>>>>
>>>>>>>>                
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>              
>>>>>>>
>>>>>>-- Davanum Srinivas : http://wso2.com/blogs/
>>>>>>
>>>>>>
>>>>>>            
>>>>>>
>>Dims,
>>
>>Yes. I totally agree. So my suggstion is that we can keep the
>>header (axis2_http_client.h) as an API for different http_clients.
>>I did one sample implementation (very basic stuff) and ppl can
>>develop using any other libraries and they have to adhere to the
>>API given in axis2_http_client.h.
>>
>>Any thoughts ?
>>
>>- Sahan
>>    
>>
>
>  
>
>>>>        
>>>>
>
>  
>
>>>
>>>-- Davanum Srinivas : http://wso2.com/blogs/
>>>
>>>
>>>
>>>      
>>>
>
>Yes Samisa. We can use the axis2_http_client.h as the abstraction.
>(which has very common functionalities to any http client such as
>send, recieve .. etc).
>  
>
OK great, then we only need to have the impls using whatever the libs we 
need.
May be we can have the libcurl impl inside 
modules/core/transport/http/libcurl then.

Samisa...

>- - Sahan
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.1 (GNU/Linux)
>Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
>iQEVAwUBQ8HkyKnIlEsDdb85AQIyUQgAm/MfQ7+sgnZjTc6fcsLAW9ddYyNtwaaT
>eB0l4TcHCyoeIYgMaBFAl2i1/lpvUbXYBe1oo3LEA4i7HCLLdAZrmPdpclG0flmm
>LbkHvwDzdgKyGJ9HeG9/mGlCI8rmlfTM8rwK6BWyo0Qhir7CMj7nVE1wa2gNq+7Y
>wo5wnOZ3WwibcLPl0wrrxZEQNABr9hKBf5Ct4S13fnFzZfUJdaHPdkYo9B40IXMk
>VYmT8kyCy2qFacQTARm850VqqF3MRjELdvZrwXvGJ5lIP/OP79XxnyNCjvnQ8XQd
>zMiu/WWF6ys6qcZNxwqum51fd2KZ63ESqjz+foRxDpnMA7yjgulvPw==
>=znyh
>-----END PGP SIGNATURE-----
>
>
>  
>


Mime
View raw message