Le 15 avr. 2013 à 16:52, Simon Fischer a écrit :
> As you said you have experience with iOS and Android, what's the better
> choice in your opinion the threaded resolver or c-ares?
I would say you could pick one or another. Maybe you should refer to this
post[1] by Daniel for more details.
In
evelopment"
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 tha
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
?
Regards,
Simon
Gesendet: Montag, 15. April 2013 um 14:46 Uhr
Von: "Cédric Deltheil"
An: "libcurl development"
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
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
Hi everyone,
I'm developing a cross-plattform app for Android, iOS and Blackberry. I'll use libcurl only for HTTP/HTTPs GETs. Right now I'm in the process of compiling libcurl for the different plattforms and reading the libcurl documentation. As I would like to keep the file size of libcurl an
