Always use the same event loop for a client connection #562
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Motivation: It might be useful for other applications interacting with gRPC to know that a client connection will always use the same event loop, event if it reconnects. Modifications: Use the same event loop when attempting reconnections. Result: A connection will only ever use one event loop.
glbrntt
force-pushed
the
same-event-loop-group
branch
from
a110c85 to
d940402
Compare
MrMage
approved these changes
Aug 23, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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:
It might be useful for other applications interacting with gRPC to know
that a client connection will always use the same event loop, event if
it reconnects.
Modifications:
Use the same event loop when attempting reconnections.
Result:
A connection will only ever use one event loop.