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 call set_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.
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.