Stephen M. Coakley

That's the way the code reads, yeah, unless there's something I am misreading that a libcurl maintainer might know better.

Note that `CURL_LOCK_DATA_CONNECT ` does not do anything until curl 7.57.0 which is somewhat recent; if running against an older version of curl this approach will still not be effective.

I'm experimenting with the share API here: #105 I understand your use case and I want to help, but I also do not want to add any configuration that isn't...

Nope, not yet, but there's an upstream issue to add support for it in the curl crate here: https://github.com/alexcrichton/curl-rust/issues/341

The first step for this has at long last landed, as the upstream curl crate now has a `rustls` crate feature: https://github.com/alexcrichton/curl-rust/issues/341. Our work on Isahc's end is not finished...

Adding "breaking" label to this, since the way Isahc 1.0 is configured, the native TLS engine is always enabled with no way of opting-out. We need to offer rustls and...

No plans currently, but this could be an interesting feature to discuss. Something planned is to replace the (unstable) middleware API with a better "interceptor" API that would allow you...

This PR is squarely in the "experimental" phase at the moment, and its API is fairly clunky. The main problem to solve here is how to allow attaching a specific...

Currently, yes this is the case. > If that is correct, shouldn't this be disabled by default, and only enabled if the application decides to do so? Is there a...

Sorry if this is too direct, but: > I cannot decide anymore if I want the "log" feature in my application or not. Why do you want to decide this?...