> From: [email protected]
> Date: Tue, 17 Aug 2010 11:01:54 +0200
> Subject: Re: Trying not to wait for reply
> To: [email protected]
>
> On 17 August 2010 08:18, Jess Hmby <[email protected]> wrote:
> > 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.
>
> It doesn't sound like your server is an HTTP server. It might be
> similar, but if it is not HTTP, then libcurl might not be the best way
> to talk to it, since libcurl talks HTTP (or FTP, etc., etc.)
>
> What protocol does your server actually speak?
>
> Also, please don't top post.
Yes, it is HTTP what my server speaks, though I'd rather say "system" instead
of server as it is a client-server-client structure. As I said is not a common
thing, I know , it is not a typical c-s talk ... but where's the fun in
programming things that are already exist ? :)
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
