Good news: There was a patch for this submitted to the internal version of
the code which should make its way to SVN today or tomorrow, and will be in
the 2.0.3 release.
On Wed, Nov 19, 2008 at 1:29 AM, Jerry Cattell [EMAIL PROTECTED]wrote:
I'm trying to use a custom EnumValueOption:
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
On Mon, Nov 17, 2008 at 17:02, codeazure [EMAIL PROTECTED] wrote:
Has anyone devised a makefile rule for the .protoc-.cc-.o sequence?
...
This appears to work well, but I was hoping it is possible to define
a .proto.cc rule to automate it by some cleverness. My project uses
Automake it is
