Hi, I am wondering what's the recommended way of doing versioning and version negotiation in gRPC? The use case I can trying to solve is:
1) I have an API server that uses gRPC. The API might have multiple versions. 2) The client has multiple versions too. 3) I want the newer version of the client to smartly pick the API version (through some negotiation) depends on the API version that the server supports. For instance, if the server exposes an older version of API, the client will choose to use the old API to talk to the server. In the REST, the standard way of supporting that is through Content-Type negotiation: https://stackoverflow.com/questions/10742594/versioning-rest-api I am wondering if there is anything equivalent in gRPC? Thanks! - Jie -- 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/1fc77d64-e01b-4a73-9f6b-41759fb9d8c7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
