On Fri, 23 Sep 2022, Dmitry Karpov wrote:
But how do you suggest to address the issues with "closed code" as I outlined in my previous post?
" - if you code integrates (or will do that future) some "3rd party" components which might be using libcurl and dual-stack resolve modes, which you can't modify"
Closed source applications that use libcurl cannot be fixed unless the creators fix their applications. This goes not only for IPv4/IPv6 issues but for all options libcurl provides.
I don't understand why do you call my proposal "a new way"?
Because it introduces both a new public API function call plus a new concept of a global callback.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
