On 8/28/25 05:53, Daniel Stenberg wrote:
> On Thu, 28 Aug 2025, Demi Marie Obenour wrote:
> 
>>> As no user has asked for it and no developer has offered an implementation, 
>>> I
>>> think we can simply defer the entire discussion.
>>
>> I thought https://github.com/curl/curl/pull/17509 was that implementation
>> (and VPN On Demand was mentioned there), so I'm a bit confused.
> 
> Oh sorry, I had not spotted that.
> 
> The way that PR was implemented I immediately lost track and interest because 
> it basically replaced half of libcurl's functionality with 
> Apple-magic-functions that work completely different and would be a serious 
> pain to support.
> 
> My fault. So there was an implementation attempt - that we coulnd't accept.

That's why I asked this question: to see if there is a solution that you
*could* accept that still made the relevant platform features work,
by using Network.framework for DNS and for layer 4 down.  To me, most of
libcurl's functionality is in the higher levels of the stack: the many
protocols it supports, the HTTP redirect handling, the stable ABI and API,
and things like that.

Obviously, you could say "yes", "no", "it depends", or even not answer at
all.  You don't owe me a response :).

Finally, thank you so much for writing curl and libcurl.  curl is absolutely
awesome and while I have not used libcurl, I know it is also awesome.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)

Attachment: OpenPGP_0xB288B55FFF9C22C1.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

-- 
Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library
Etiquette:   https://curl.se/mail/etiquette.html

Reply via email to