Design and implement client Channel class hierarchy #2496
Merged
Conversation
This file contains 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
…s that encapsulates all ZMQ connection/request logic Bears-R-Us#2495
stress-tess
reviewed
Jun 13, 2023
jaketrookman
approved these changes
Jun 13, 2023
|
@Ethan-DeBandi99 @pierce314159 @jaketrookman @TheOddCzar789 Updated per Pierce's comments and retested to ensure everything still works:
|
stress-tess
approved these changes
Jun 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #2495
This PR encompasses the design and implementation of a client Channel class hierarchy that fosters support of client/server communication via protocols other than ZMQ, starting with gRPC