Hi Daniel, I couldn't do that because I am never going to receive a response (in the client) coming from that connection. I partially solved the problem setting a timeout (CURLOPT_TIMEOUT) but it is not a nice way in mi opinion because it's time that I loose there and I dont think it is safe.

> Date: Mon, 16 Aug 2010 19:16:12 +0200
> From: daniel_at_haxx.se
> To: curl-library_at_cool.haxx.se
> Subject: Re: Trying not to wait for reply
>
> On Mon, 16 Aug 2010, Jess Hmby wrote:
>
> >>> Hi, is there a way to tell curl not to wait for the server's reply?
>
> > Hi, yes I know it is awkward, I am trying several uncommon things these
> > days. The idea is to send a response later from that third server. It would
> > also be useful for HTTP/RTSP tunelling. So to do that hang up you suggest is
> > there a specific way to do that with libcurl or should I do it directly ?
>
> You can make your progress or write callback abort as soon as you've received
> the first byte, thus cancelling the reading of the response.
>
> --
>
> / daniel.haxx.se
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html
                                               

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-08-17