For an async C++ server, the method declaration generated by the C++ protoc plugin takes two completion queues: new_call_cq and notification_cq. The former is declared as a more derived ServerCompletionQueue*, the latter is "just" a CompletionQueue*. I'm in the habit of using one CQ for both, which I likely picked up from the async hello world example. This works, so I do not fix it.
But for the life of me, I could not find any information why the async interface accepts two CQs, and what are the use cases which benefit from two separate CQ w.r.t. a call. Any info out there? -kkm -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/d5754f98-6711-45ff-9000-b178e457d9can%40googlegroups.com.
