feat(grpc): support encoding/decoding messages #2395
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
arjan-bal
force-pushed
the
grpc-channel
branch
from
833d275 to
6db43f6
Compare
arjan-bal
force-pushed
the
grpc-channel
branch
from
6db43f6 to
1721c96
Compare
arjan-bal
force-pushed
the
grpc-channel
branch
from
7ba950e to
39165c6
Compare
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.
This PR add methods on the Message trait to support encoding/decoding messages. It is the responsibility of the transport to call these new methods. This allows the in-memory transport to transfer objects without serialization. An
Allocatortrait is introduced to create response messages in an object safe way. The usage of theAllocatoron the server is missing, a NoOp implementation is used to avoid build failures.