Open
Description
gRPC supports two flavors of asynchronous callbacks -- from their documentation:
https://grpc.io/docs/languages/cpp/callback/
gRPC C++ offers two kinds of APIs: sync APIs and async APIs. More specifically, we have two kinds of async APIs: the old one is completion-queue based; the new one is callback-based, which is easier to use.
Since we want to implement the service using the callback APIs, the service interface we should implement is RouteGuide::CallbackService.
I'm wondering how large of an effort it is to extend flatbuffers gRPC C++ codegen to generate the necessary functions for interacting with the CallbackService
implementation?
Metadata
Metadata
Assignees
Labels
No labels