Is it possible for one server thread to block (Next()) on multiple completion queues? I am thinking along the lines of an API that invokes an underlying select() that can monitor multiple RPC channels, waiting to see which of the underlying channels become ready.
--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/491a9fa0-bb22-4a88-be8f-fcb264d8e453%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Currently, it is not possible to do this. May consider exposing a select'able interface at some point (but no plans in the near-future)thanks,-Sree
On Thu, Aug 31, 2017 at 12:31 PM, <akshitha...@gmail.com> wrote:
Is it possible for one server thread to block (Next()) on multiple completion queues? I am thinking along the lines of an API that invokes an underlying select() that can monitor multiple RPC channels, waiting to see which of the underlying channels become ready.
--
You received this message because you are subscribed to the Google Groups "grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+u...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscribe@googlegroups.com.
To post to this group, send email to grp...@googlegroups.com.
Visit this group at https://groups.google.com/group/grpc-io.
To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/bf433ec3-690d-47cb-a700-4875da571d94%40googlegroups.com.