OK, now you've confused me :-) I don't understand the exact relationship between all these classes, which is why I'm asking the question. If I want to build an application where I have a number of services that share a single TCP port, what organisation do I need to use?
You mention multiplexing services - what does that mean for a client application using the connection? A UML:diagram (or similar) showing the relationship between controllers, channels & services would really aid my understanding of how this system would operate. Perhaps these terms are in common usage in other RPC systems, but because I haven't used any, I'm uncertain about what these entities do. I've read the documentation several times, but the overview of how it works hasn't clicked. Thanks, Jeff On Nov 20, 12:54 pm, Kenton Varda <[EMAIL PROTECTED]> wrote: > 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 what you were thinking of? A > single RpcChannel represents a connection to a single Service. However, > there's nothing stopping you from multiplexing multiple RpcChannels across a > single TCP connection, or creating a protocol that allows you to choose > between multiple services exported by a server when constructing an > RpcChannel. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to email@example.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---