curl-library
Aw: Re: Re: libcurl for Android, iOS, Blackberry - c-ares and CURLOPT_NOSIGNAL option
From: Simon Fischer <fischer.simon_at_gmx.at>
Date: Mon, 15 Apr 2013 16:52:02 +0200 (CEST)
Date: Mon, 15 Apr 2013 16:52:02 +0200 (CEST)
Thanks again Cédric, I understand now. As you said you have experience with iOS and Android, what's the better choice in your opinion the threaded resolver or c-ares?
Regards,
Simon
Gesendet: Montag, 15. April 2013 um 15:23 Uhr
Von: "Cédric Deltheil" <cedric@moodstocks.com>
An: "libcurl development" <curl-library@cool.haxx.se>
Betreff: Re: Aw: Re: libcurl for Android, iOS, Blackberry - c-ares and CURLOPT_NOSIGNAL option
Von: "Cédric Deltheil" <cedric@moodstocks.com>
An: "libcurl development" <curl-library@cool.haxx.se>
Betreff: Re: Aw: Re: libcurl for Android, iOS, Blackberry - c-ares and CURLOPT_NOSIGNAL option
Le 15 avr. 2013 à 15:03, Simon Fischer a écrit :
I have one more question, sorry if this is a stupid one. :) As I understand it now if I build with the threaded resolver I will than use the multihandel and libcurl will manage the threads? And if I choose c-ares I manage the threads? Is this right?
No. Building libcurl with the threaded resolver or c-ares only impacts (as their name indicates) the *internal* DNS resolution performed by libcurl when a transfer is to be done. In other words this is transparent for you.
On your side you may want to use the multi interface or multiple threads as different alternatives to perform parallel transfers - according to your use case and constraints of course.
That being said, if you decide to go ahead with threads (managed on your side!) you should take care to use libcurl with the correct options (which is what we are discussing here!).
Cédric
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-04-15