Buy commercial curl support. 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 Daniel himself.
Re: Network.framework and libcurl
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Demi Marie Obenour <demiobenour_at_gmail.com>
Date: Thu, 28 Aug 2025 07:36:22 -0400
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.
Received on 2025-08-28
Date: Thu, 28 Aug 2025 07:36:22 -0400
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)
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
- application/pgp-keys attachment: OpenPGP public key
- application/pgp-signature attachment: OpenPGP digital signature