You have 3 parties, A, B, C
When A calls B, and it returns a capability X on C, handoff can be done
So B tells C to expect A, and tells A to go to C and pick up the reference.
This way all further calls on X doesn’t go through B but directly from A to C
must be for distributed systems
yes, that was the idea. the RPC protocol was a bit too complicated for some use cases though, and so at least in the capnp-go community at least there is work on a more lightweight protocol that can be stateless depending on the use case + simpler to port while preserving a majority of the features and use cases
