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: Frederik Seiffert via curl-library <curl-library_at_lists.haxx.se>
Date: Tue, 31 Jan 2023 09:58:13 +0100
Hi Dan,
> Am 20.01.2023 um 18:53 schrieb Dan Fandrich via curl-library <curl-library_at_lists.haxx.se>:
>
>> Unfortunately it seems that in some cases when using multi handles this "close
>> socket function" is not being used, so I don’t think this approach would fully
>> work atm:
>> https://github.com/curl/curl/blob/f8da4f2f2d0451dc0a126ae3e5077b4527ccdc86/lib/asyn-thread.c#L409-L410
>
> That's a special case, but an interesting one. I'm not sure if that use
> overlooked the socket callback functions, or if it was added with the idea
> being that since the socket isn't used for data transfer, it doesn't need to
> use the callbacks. In any case, you can easily stop use of that socket by
> compiling with a different resolver.
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"?
Thanks!
Frederik
Date: Tue, 31 Jan 2023 09:58:13 +0100
Hi Dan,
> Am 20.01.2023 um 18:53 schrieb Dan Fandrich via curl-library <curl-library_at_lists.haxx.se>:
>
>> Unfortunately it seems that in some cases when using multi handles this "close
>> socket function" is not being used, so I don’t think this approach would fully
>> work atm:
>> https://github.com/curl/curl/blob/f8da4f2f2d0451dc0a126ae3e5077b4527ccdc86/lib/asyn-thread.c#L409-L410
>
> That's a special case, but an interesting one. I'm not sure if that use
> overlooked the socket callback functions, or if it was added with the idea
> being that since the socket isn't used for data transfer, it doesn't need to
> use the callbacks. In any case, you can easily stop use of that socket by
> compiling with a different resolver.
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"?
Thanks!
Frederik
-- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2023-01-31