The method name choice is essentially stable since all supported languages interop with the same method names. That said, the existence of classes like RpcMethod is an internal detail and could change (just like all other details in the codegen output that are language-specific).
On Wednesday, June 7, 2017 at 11:02:17 AM UTC-7, [email protected] wrote: > > Hey guys, > > Please don't mind if you've seen the same question on the Gitter channel > before. > > I'm writing a function template handling multiple async gRPC calls in C++, > and I saw that in the generated .grpc.pb.cc file there is an array of > method names like > "/package.Service/Method" (I assume it represents the endpoint of the RPC > handler?) > that are used to create RpcMethod objects in the stub implementation. > I was wondering if this is considered as internal details that might > change over different versions, > or if I can generate the same strings and create RpcMethod objects in my > function to avoid using > &Service::Stub::AsyncMethod safely. > > Thanks, > Chun-Hung > -- 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 post to this group, send email to [email protected]. 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/64b6d5ae-51e9-41d5-a320-f5d5f919c281%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
