Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Close sockets asynchronously when using libdispatch (GCD)
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Dan Fandrich via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 31 Jan 2023 08:52:36 -0800
On Tue, Jan 31, 2023 at 09:58:13AM +0100, Frederik Seiffert wrote:
> Could you please explain what you mean by "compiling with a different resolver"? I didnąt see any build options like that. Do you maybe mean building with "CURL_DISABLE_SOCKETPAIR"?
I mean using the --disable-threaded-resolver or --enable-ares configure options
(or whatever the cmake equivalent is) to use a different DNS resolver. I
thought that it was only the default threaded resolver that used a socketpair,
but in looking through the code it seems that curL_multi_poll() also uses it so
that function would need to be avoided to avoid its use.
Date: Tue, 31 Jan 2023 08:52:36 -0800
On Tue, Jan 31, 2023 at 09:58:13AM +0100, Frederik Seiffert wrote:
> Could you please explain what you mean by "compiling with a different resolver"? I didnąt see any build options like that. Do you maybe mean building with "CURL_DISABLE_SOCKETPAIR"?
I mean using the --disable-threaded-resolver or --enable-ares configure options
(or whatever the cmake equivalent is) to use a different DNS resolver. I
thought that it was only the default threaded resolver that used a socketpair,
but in looking through the code it seems that curL_multi_poll() also uses it so
that function would need to be avoided to avoid its use.
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2023-01-31