[grpc-io] [gRPC/C++] Single threaded server via select()?

What's the easiest way of making a gRPC server that can run single-threaded in cooperation with other file-descriptor based operations? What I plan is a single threaded server that waits on available data on any number of file descriptors via select(), one of the file descriptors corresponding

[grpc-io] Re: Question of example greeter_async_server.cc [multiple services -- how to handle?]

Hi Thomas, I have the exact same question! I'm wondering if I can simply call RegisterAsyncService for each service I want to handle, and then maybe start off each service "handler" with a unique tag, using the tags to demux the requests when they arrive in the completion queue. If I don't se

[grpc-io] Re: Question of example greeter_async_server.cc [multiple services -- how to handle?]

Thanks! On Thursday, November 3, 2016 at 11:55:05 PM UTC-4, sa...@portsip.com wrote: > > Hi RK, I have make a wrapper for the async base on the official example > for demux the requests, you can found it at > https://github.com/pengweichu/async_grpc_wrapper, in that example I have > added anoth

[grpc-io] [C++/Async/Streaming] What is the correct declaration for responder_ when using async/streaming?

Re: https://groups.google.com/forum/#!topic/grpc-io/hUYIjv97Hhc "C++ async API" I'm trying to use async messaging and streams. I've used the ideas from the above post, namely, creating a CallData class per RPC method (I called mine "Context" instead of CallData, and it inherits from a base cla

[grpc-io] Re: [C++/Async/Streaming] What is the correct declaration for responder_ when using async/streaming?

Ok, progress is being made -- I now have the declaration fixed up, but now I'm getting a "pure virtual method called" -- it looks like it's in the Next() handler... Here's the backtrace and code: *Program received signal SIGABRT, Aborted.* *0x0035ce0325e5 in raise () from /lib64/libc.so.6*

[grpc-io] [C++/async/stream] getting "pure virtual method called" in grpc_completion_queue_next ()

Hi all, I've created a tiny code sample that is based off the hello world async greeter example. I keep getting a "pure virtual method called" in the grpc_completion_queue_next() function, and I'm having a hard time understanding why. What am I doing wrong? I've included the proto file, C++ c

Re: [grpc-io] [C++/async/stream] getting "pure virtual method called" in grpc_completion_queue_next ()

Ok: *(gdb) handle SIG36 noprint* *SignalStop Print Pass to program Description* *SIG36 NoNo Yes Real-time event 36* *(gdb) run* *Starting program: /.../minfail* *[Thread debugging using libthread_db enabled]* *D1115 13:59:40.187940393 34391 env_lin

Re: [grpc-io] [C++/async/stream] getting "pure virtual method called" in grpc_completion_queue_next ()

Sadly, I'm still stuck. I don't know enough C++ to be able to diagnose this further... :-( On Tuesday, November 15, 2016 at 2:01:50 PM UTC-5, rkr...@gmail.com wrote: > > Ok: > > *(gdb) handle SIG36 noprint* > *SignalStop Print Pass to program Description* > *SIG36 No

Re: [grpc-io] [C++/async/stream] getting "pure virtual method called" in grpc_completion_queue_next ()

OK, tracked it down to grpc-1.0.0/include/grpc++/impl/codegen/completion_queue_tag.h -- the pure virtual function "bool FinalizeResult()" -- what do I need to do to initialize it that I'm not doing in the program above? (As a hack, I just had it print a message to stdout and return "false", no

Re: [grpc-io] [C++/async/stream] getting "pure virtual method called" in grpc_completion_queue_next ()

Woo hoo! That fixed it! Thanks Sree. Cheers, -RK On Thursday, November 17, 2016 at 2:58:59 PM UTC-5, Sree Kuchibhotla wrote: > > > Looks like you are doing two async operations together in your server: (in > calldata when status == PROCESS) > > *responder_.Write (reply_, this);* > *

[grpc-io] [c++] How to access nested message defined inside of another message?

I'm having a hard time figuring out how to access a nested message that's defined *within *a message (inline definition). However, I can easily access a nested message that's defined *outside* of the message. What I mean is: *message outer* *{* *global foo = 1;* *message inner* *{*

Re: [grpc-io] [c++] How to access nested message defined inside of another message?

yes -- that was it. Thank you! For future readers: *message outer* *{* *global foo = 1;* *message inner* *{* *int64 j = 2;* *}inner inside_message = 3;**}* *message global* *{* *int64 k = 3;* *}* On Monday, November 28, 2016 at 1:12:12 PM UTC-5, Christian Riva