feat: Allow providing custom connector to balanced channels by exposing Channel::balance
#2197
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.
Motivation
I have a requirement to balance client gRPC requests via different connectors.
There is currently no API to construct a balanced
Channel
using a custom connector (it is possible to create aChannel
with a custom connector usingEndpoint::connect_with_connector_lazy
).Solution
There is currently an internal constructor
Channel::balance
with the following signature:Since
Connection
is a private type this PR modifies the signature to:This signature supports all internal uses of
Channel::balance
while allowing maximal flexibility for advanced use cases.