Thanks for clearing the confusion here. Obviously i am linking to the*libcurl.dylib *which is Mac OS X provided.
For now what would be the best solution so as to overcome the hang issue? Should i build the curl on my own for Mac OS X 10.8.3 Mountain Lion and link the same with my daemon ? thanks, ~Arjun On Tue, May 28, 2013 at 5:44 PM, Daniel Stenberg <[email protected]> wrote: > On Tue, 28 May 2013, Arjun SM wrote: > > Also i dug deep into the functions from the sample, i found out that >> *Curl_resolver_wait_resolv() function should not be used *since using this >> risk getting the multi interface to "hang". This function is getting called >> from Curl_do_perform() >> > > If your libcurl is built to use the synchronous name resolver back-end, > then yes it can be synchronous and then a single transfer's name resolve > will block the others. > > That's why we provide two other (asynchronous) resolver backends to allow > you to build a libcurl that doesn't block when doing DNS operations. > > Unfortunately, most users will be left to using a libcurl someone else > built for them and then of course you can't select which backend to use > (until one future day we allow it to be selectable in run-time). > > -- > > / daniel.haxx.se > > ------------------------------**------------------------------**------- > List admin: > http://cool.haxx.se/list/**listinfo/curl-library<http://cool.haxx.se/list/listinfo/curl-library> > Etiquette: > http://curl.haxx.se/mail/**etiquette.html<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
