Dear all, I have a gRPC service that provides results that can be localized. I am using gRPC as well as the grpc-gateway to automatically generate a REST service running in parallel.
The usual way of specifying locale preferences in REST services is via Accept-Language tags. As this is, strictly speaking, part of the API contract, does it make sense to write a gRPC service description that explicitly documents this parameter. I could therefore easily add a "string language_preferences=2" to the request message definition? If so, is there a clever way to populate this in the grpc-gateway much like URL parameters? Or is there a better way of handling language preferences in grpc and grpc-gateway? Many thanks, Mark -- 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/8033c8e1-2516-40b2-889d-60885ca77419%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
