On Thu, Mar 17, 2016 at 1:42 PM, Gwen Shapira <g...@confluent.io> wrote:
> "I think I would make this approach work by looking at the released server > version documentation for each version that I am trying to support and test > against*, manually identify the expected "protocol vectors" each supports, > store that as a map of vectors to "broker versions", check each vector at > runtime until I find a match, and write code compatibility checks from > there." > > How is this better than a global version ID? As a client developer, it seems roughly the same. I think it probably avoids the server development workflow issues, and possibly the need to agree on semantics of the global version ID? But others surely are more qualified than me to comment on that part. -Dana
