Thank you Kenton Shane - it must have been a slow brain day for me
yesterday :-)
I confused the underlying implementation with what PB provides. The
RPC system doesn't know or care how data is transferred.
On Nov 20, 5:56 pm, Shane Green [EMAIL PROTECTED] wrote:
It sounds like the system in
On Nov 20, 7:58 am, Kenton Varda [EMAIL PROTECTED] wrote:
I'm not sure I understand. There's nothing stopping you from spreading your
definitions out among multiple .proto files which import each other, and
there's nothing stopping you from exporting multiple services from a single
server.
RpcController objects are per-request, not per-server or per-service. For
every RPC request you make, you should have another RpcController object
(though you can reuse an object by calling Clear() as long as you aren't
making two requests at once).
RpcChannel objects are per-service. Is that
Thanks for the breakdown, that's very helpful. I had some trouble
finding details about how the PB RPC terminology mapped to what I'm
familiar with.
It sounds like the system in question has a single public service with
delegates calls to back-end services, distributed across machines
available
