On Wed, Oct 30, 2019 at 1:29 PM Newbugreport <[email protected]> wrote:
> Thank you for your replies, Kenton and Ian. > > Kenton, I'd like to contribute a new sample to help new users. I don't use > GitHub but I can email you the work. The sample would be tutorial-oriented > and not use ez-rpc. I'll look through the ez-rpc source to see how it uses > the other classes, though any tips or insight would be appreciated. > Cool! But it would be really helpful if you could create a GitHub account and submit as a pull request. That way the git history will show you as the author, we'll have a public record of the conversation around the submission, and we can use the GitHub pull request interface to do a code review. I'm working on my own project, and I have capnp working and my five > services are all talking to each other. Two of the services in particular > do a lot of relaying, in one case three services provide the same interface > and one query would get relayed from one to another to another. Is there a > way to efficiently forward these queries and responses? I'm trying to see > how to forward efficiently in terms of single messages (copying, processing > time) and also in terms of many messages (not blocking one message while > waiting for a response from another). > With Cap'n Proto, you can freely pass a capability across multiple RPC hops and it will automatically set up proxying that is as fast as possible. In the future, I intend to extend the protocol so that when you forward a capability, the eventual client will automatically form a direct connection to the server, to avoid proxying. The RPC protocol actually already contains a spec for this, it just hasn't been implemented yet. -Kenton -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/capnproto/CAJouXQnQL8COwFeDon5Yo1Av6%2BVJSYuUfyksRcHmiXKU%2BAhg0A%40mail.gmail.com.
