On Mar 20, 2012, at 16:12 , Mick wrote: > These objects are going to be accessible to multiple users, who's accessor > programs may be on different release cycles. I have been looking into > protocol buffers as a way of managing dataloss/corruption between versions. > Has anyone used protocol buffers to approach this type problem before?
I'm not quite sure what you mean and what information you are looking for. However, protocol buffers were designed to help with this sort of problem, but it still requires care to make it work. Random notes off the top of my head: * You may want to make all fields optional, since if a message is missing a required field it will fail to parse. Certainly all *new* fields *must* be optional. * Protocol buffers only help with the parsing. You still need to think about forward and backwards compatibility (eg. how is your software going to process the messages). * Passing messages through (eg. proxies or other tools) will work. Hope this helps. Good luck, Evan -- http://evanjones.ca/ -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to protobuf@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
