I've benefited from a lot of third-part documentation on schema design in Protobufs and from the work that's been put into supporting forward and backward compatibility. One edge case that we at Conductor have run into in a couple of places involves enums. Unlike a lot of other incompatibilities, it's pretty easy to make incompatible schema changes to enums without any of your usual tools helping you; in particular the generated code before and after a change to allowable enum values will typically not raise compilation errors. I've tried to gather up some of our experiences and possible workarounds that reduce the chance of unexpected incompatibilities in a blog post.
Would appreciate any review and comments / corrections. Please shout out with any errors you see. http://bit.ly/1boyizy Thanks! -Josh -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to protobuf+unsubscr...@googlegroups.com. To post to this group, send email to protobuf@googlegroups.com. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/groups/opt_out.
