Implement Results::set_pipeline()
#515
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
This provides the same functionality as capnproto-c++'s `CallContext::setPipeline()`, but with a slightly different API. Whereas in capnproto-c++ `setPipeline()` requires usage of a PipelineBuilder, here we just re-use the existing Results message.
dwrensha
force-pushed
the
set-pipeline
branch
from
150288f to
baf662f
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 provides the same functionality as capnproto-c++'s
CallContext::setPipeline(), but with a slightly different API.Whereas in capnproto-c++
setPipeline()requires usage of a PipelineBuilder, here we just re-use the existing Results message. You callset_pipeline()after you've filled in the capabilities in the result message, and then the RPC system is allowed to start running pipelined calls on the capabilities.