feat: allow passing custom http client #75
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Eppo Internal:
ποΈ Fixes #74
π Design Doc: link if applicable
Motivation and Context
To allow tuning the HTTP client, such as TCP transportation config, to fix the issue reported in #74.
Description
With this change, when we initialize the Eppo client, we can pass in a custom HTTP client like this:
This parameter is optional, and if we don't specify it, the default behavior will be applied.
With the above config, the netstat output will look like this, where we have multiple TCP connection rotated.
How has this been documented?
How has this been tested?