Thank you for the reply. > ... Also all servers will > need to be updated before releasing it in the clients. > > Always make sure that each client can work with the current server version > and the next server version. Serves must work with the current client and > the next client. This forms a chain of compatibility that makes rolling out > new versions easy and makes rolling back safe!
But in the roll-back scenario if you only have control over the server you could still get into the situation where the client has a newer version than the server, right? So it's still necessary for some form of negotiation. The client needs to figure out that "DoItWayThree" won't work and fall back to "DoItWayTwo". Right now, at least with the Go libraries, the only way to implement all of this is a lot of boilerplate. I'm hoping there's a better way. Thanks, ~ Scott -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAJrQjSuOCWENJzmo-3%2BPjp0JfTguF1pGV2xfGUgYip7tvPu%2BMA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
