Re: [protobuf] Compiler forward-compatibility

Yes, absolutely. The schemas do not even have to be exactly the same, and in fact protobuf is designed to allow the schema to evolve in a compatible way. The most important thing is just to never reuse the same field number with incompatible types. On Fri, Jan 18, 2019 at 2:30 AM Nikita Vorobyev

[protobuf] compile error no matching function for call to 'Acquire_Load()

I have built protobuf-lite and in trying to link a gRPC client I receive the following error: "/usr/local/include/google/protobuf/stubs/once.h: In function 'void google::protobuf::GoogleOnceInit(google::protobuf::ProtobufOnceType*, void (*)())':

Re: [protobuf] Java Date object to be added in .proto file

There are the well-known types , which include google.protobuf.Timestamp: syntax = "proto3"; import "google/protobuf/timestamp.proto"; message Product { google.protobuf.Timestamp last_ordered_date = 1; } Sadly,

[protobuf] Java Date object to be added in .proto file

HI, I have a Date java object that I want to add in .proto file. I use Proto3. Is there any exisitng proto Datatype that I can use? Please advise at the earliest. Ex: message Product{ optional date last_ordered_date = 1; } where last_ordered_date='2019-01-15' Thanks, Shilpa -- You

[protobuf] Compiler forward-compatibility

Hi all! Is protobuf compiler-neutral? Will I be able to deserialize message with code, generated by compiler of version X, if this message was serialized with compiler of version Y? Version of syntax and schemes will be obviously the same on both sides. Thanks in advance. Nikita. -- You