On 5 January 2011 17:57, amit paliwal <amit.ambitions_at_gmail.com> wrote:
>
> On Wed, Jan 5, 2011 at 10:36 AM, Daniel Stenberg <daniel_at_haxx.se> wrote:
>>
>> On Wed, 5 Jan 2011, amit paliwal wrote:
[...]
>>> But I thought Curl can still handle TLS authentication while sending and
>>> receiving from network, even if i use curl_easy_send() and curl_easy_recv().
>>
>> It does. But the moment you curl_easy_send() or curl_easy_recv() you've
>> abandoned all other protocol support libcurl can offer and you are entirely
>> on your own. IMHO, doing that with a plain HTTP based protocol is unwise.
>
> I agree and in fact it is my main concern here. I need curl to handle http
> and TLS on behalf of me, and as you mentioned it can handle TLS but not HTTP
> if I do proprietary stuff.

What you are describing is not HTTP. It is similar to HTTP, but it is not HTTP.

By the way, I am interested if you already have a server that you are
trying to talk to or if you still need to create the server.

-- 
Michael Wood <esiotrot_at_gmail.com>
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html