Oh, if all you're worried about is compatibility then I would definitely
upgrade to the latest version (currently 3.4.1). We take great care to
preserve wire format compatibility and so all your existing serialized
messages will be readable with the latest protobuf version. You just have
to make
Yes, very early on during initialization of the library. My only concern
with upgrading to a new version of protobuf is backward compatibility.
Should I stick with 2.6 or go with 3.x? I know I can't use any of the new
features but will all my current messages be recognizable across the
When you say early on in application initialization, do you mean before
main() begins? Because if so then that might make things a little more
complicated. Using the non-lite version would probably not help very much
with debugging, since actually it adds more complexity by including
descriptors.
Hey all,
I am using 2.4.1-lite in an embedded project. I know it is a bit old but it
is what I have to live with for now. We send a message simple synchronous
request from one application to another to get a list of files. It returns
the following message.
message return_m {
optional
