It would be nice to have a migration guide (checklist) somewhere, like: 1. All fields should be optional. 2. Do not use custom defailt values. 3. All enums should have first element with tag = 0. 4. Do not use extension for anything except custom options.
Something else? On Friday, April 29, 2016 at 1:18:12 AM UTC+3, Feng Xiao wrote: > > > > On Tue, Apr 26, 2016 at 7:04 PM, Bo Gao <[email protected] <javascript:>> > wrote: > >> suppose server side is updating into protobuf3, but client side still use >> protobuf2, can then communicate will? >> > Yes, as long as you only use proto3 features, they are wire compatible. > > >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/protobuf. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
