-
Notifications
You must be signed in to change notification settings - Fork 193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optionally Pass in the ConnectionContext when creating the TLS Manager #228
Comments
Check out #227, which has a very similar flavor to this. That PR is blocked on some understanding around laziness of creation, but simply providing a |
I looked closer at the code and see the new I'm not currently blocked by this FWIW, but will either have to fork http-client temporarily or will become blocked in the next few weeks. |
In that case, I may as well expose |
I just pushed a commit to master with this, want to check it out before I release? |
LGTM
|
Awesome, released. I'll rebase the other branch on top of this. |
For profiling purposes I need to create many (~1000) separate Managers. This is fine for HTTP, but if I need TLS I run into memory and performance issues due to the slow and expensive creation of the ConnectionContext.
I would like to be able to create a single certificate store and share it between Managers.
One way to enable this would be to modify the current mkManagerSettings
Alternatively a new function for creation could be added
The text was updated successfully, but these errors were encountered: