curl-library
Aw: 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 15:03:29 +0200 (CEST)
Date: Mon, 15 Apr 2013 15:03:29 +0200 (CEST)
Thank you Cédric, I understand it better now.
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?
Regards,
Simon
Gesendet: Montag, 15. April 2013 um 14:46 Uhr
Von: "Cédric Deltheil" <cedric@moodstocks.com>
An: "libcurl development" <curl-library@cool.haxx.se>
Betreff: 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: libcurl for Android, iOS, Blackberry - c-ares and CURLOPT_NOSIGNAL option
Le 15 avr. 2013 à 14:26, Simon Fischer a écrit :
Does somebody know if Android, iOS and Blackberry are some of these plattforms where libcurl will not function properly multi-threaded without this option set?
From my own experience on iOS and Android platforms only, if you build libcurl without async DNS support, you will encounter (rare) random crashes in this precise context.
For more details, please refer to this recent discussion on the list:
And what do you think do I need c-ares or not? I'm planning on running each request in his own thread.
As the doc says, you can:
1/ build libcurl with threaded resolver or c-ares[1]
2/ or enable the CURLOPT_NOSIGNAL option otherwise
Cédric
[1]: e.g on iOS, Nick Zitzmann provides a libcurl build with the threaded resolver: http://seiryu.home.comcast.net/~seiryu/libcurl-ios.html
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2013-04-15