And what about a mixture: will (Java) classes generated by 2.4.1 work with
the 2.5.0 library ?
Op maandag 12 januari 2009 18:42:41 UTC+1 schreef Kenton Varda het volgende:
Just to add an official response: Yes, they will be compatible. If they
weren't, we would consider that a very serious
On Thu, Mar 14, 2013 at 1:42 AM, Ernest Micklei ernest.mick...@gmail.comwrote:
And what about a mixture: will (Java) classes generated by 2.4.1 work with
the 2.5.0 library ?
No. Only serialized data is ensured to be wire-compatible across all
protobuf versions, not the generated code. The
Thank you for confirming this.
^ Ernest
Op donderdag 14 maart 2013 21:35:00 UTC+1 schreef Feng Xiao het volgende:
On Thu, Mar 14, 2013 at 1:42 AM, Ernest Micklei
ernest@gmail.comjavascript:
wrote:
And what about a mixture: will (Java) classes generated by 2.4.1 work
with the
shanibr...@gmail.com wrote:
Hi,
Lets say my proto (abcd.proto) is compiled with the protoc compiler
version 2.0.3 and my application also links to the corresponding
runtime libraries. I now run my app and store the bytes generated
from the proto object to some persistent store (say a
If you think about it, what you describe is not much different to if
I write the binary using C++, can I read it with java / C# /
ActionScript / etc - since they all have different code describing
the same binary wire-format.
The answer is: yes, (assuming there are no significant bugs between
This was a minor concern to me as well and I did try (for sanity's
sake) persisting the binary objects while upgrading my app to newer
versions of the protobuf library and reading the persisted objects
worked like a charm. Like Marc mentions, the underlying binary spec
has to be the same if it is
