On 08/26/2010 01:56 PM, Bryan Duxbury wrote:
This all sounds really cool, except that there is more than one kind of protocol. Further, I don't think we should *ever* break binary compatibility with a protocol. The cost is simply too high.
FWIW, I started out Avro with 1.0 so we never had to argue when it was ready to go 1.0.
For Avro we use roughly FORMAT.API.PATCH. In other words, 2.0 could make an incompatible change to a binary format, but hopefully we'll never have a 2.0 release. Incompatible API changes are generally discouraged, but permitted in minor releases. Patch releases can include new features and bugfixes, but no incompatible API changes.
Doug
