Daniel Stenberg

> This branch cannot be rebased due to conflicts Rebase your branch onto master and force-push instead of merging master into your branch.

I think it would be sensible to make the first steps include these: 1. Make sure the build does not impact other backends 2. Document the backend as experimental and...

> Use availability annotations to allow fallback from Network.framework to other implementations (Secure Transport, etc) when running on pre-2021 OS versions Secure Transport is being dropped from curl next week....

It is probably impossible to use the network framework as a TLS backend in libcurl without sacrificing a first-born and accepting that lots of curl features can't be done. I...

If there is an existing *alive* connection to a host, libcurl will try to reuse that connection unless you tell it otherwise. In this scenario it sounds as if that...

> it would be really great if libcurl had some kind of option that users could use to inform it that it shouldn't reuse existing connections and future requests should...

Thanks! Here are some good next steps: 1. Update docs/libcurl/symbols-in-version 2. Provide at least one test case that shows the feature working 3. Add documentation so that we can verify...

I have a proposal for solving this slightly differently: We introduce a new value to the existing `CURLOPT_FRESH_CONNECT` option. Currently this option uses the value `1` and means that *this*...

#17613 is a proposed replacement of this

> Hence removing the write limit applied by curl's calling code, would lead to larger chunks being transferred in one go, potentially leading to faster transfers. What limit is this...