thanks for the solution buddy. Due to project deadlines, I had to go on with
the sync version, I've also implemented a very simple templated version of it
which needs improvements. I will post it in here in free time.
--
You received this message because you are subscribed to the Google Groups
Hi White,
1. Is it possible that you abstract and implement your actual calls
outside the grpc framework. You can still use protobuf to organize your
calls, instead of defining a lot of grpc methods, you define only one
async grpc method streaming on both sides. In the streamed mes
Thanks for raising this issue. We currently don't have any solution for
this since each method type needs to be requested separately at an async
service. It seems like it would be a useful add-on but we have no API-level
approach for this.
On Friday, March 16, 2018 at 3:13:02 AM UTC-7, White Sw
Check out the example I added
at https://groups.google.com/forum/#!topic/grpc-io/T9u2TejYVTc
As for 300-400 rpcs, you can write a custom code generator that plugs in to
ProtoC (much like grpc_cpp_plugin) and have it generate additional code
that you may need (like auto "requesting" your server
You say micro-services and then say your server will have 300-400 rpcs? Are
they part of the same service or many independent services and you are just
trying to get a common framework together?
I had a similar problem in my application which is/was largely a monolith
and I had to add gRPC supp
