[protobuf] pros and cons to upgrade protobuf v3

Hi, I had a debate with my colleagues regarding to upgrade protobuf v3 because I'd like to use MessageToJsonString and JsonStringToMessage for GUI development of web application and mobile app, but my colleagues are not convinced, they argued GO can do it very easily and they are worrying about

[protobuf] providing a default value for Timestamp attribute

Hi, I have a Timestamp attribute in a protobuf type. Is there an "easy" way to automatically set this attribute to System.currentTimeMillis() when an instance of the protobuf type is created ? Thanks, Jorg -- You received this message because you are subscribed to the Google Groups "Protocol

Re: [protobuf] pros and cons to upgrade protobuf v3

You can use the latest version but still use a corpus files syntax="proto2" files. Marking required fields as optional is not the only difference (and, in proto2, that is not a particularly safe operation -- you must be certain you've updated *all* readers of those messages with the new definition

[protobuf] Including C++ header files for proto file that include multiple proto files inside it..

Hello there. I have a proto file that include other proto file inside or linked to it. Do i need to include the generated header files for those proto in my client implementation or they are linked automatically to my single proto file. Or heres more clearly A proto file contains B proto and C

[protobuf] Contribution Guide?

Hi all! I'm curious if there is a contribution guide for protobuf, or anything I should be doing to help get my patch merged. It is very small and fixes a build error in our (warning-aggressive) environment at $DAYJOB. I've created an issue - https://github.com/google/protobuf/issues/3356 and

[protobuf] Generated C++ doesn't compile with #include header error

I have a directory hierarchy of protos, like: dirA/a1.proto dirA/a2.proto dirB/b1.proto dirB/b2.proto Using protoc, the generated C++ file has issues with including the header a1.pb.h from its a1.pb.cc file. Generated code in a1.pb.cc looks like: // Generated by the protocol buffer compiler.

[protobuf] Re: Generated C++ doesn't compile with #include header error

Obviously if I were to edit the proto file for the include to: #include "a1.pb.h" it works fine. On Friday, July 14, 2017 at 10:39:11 AM UTC-7, Ronak Shah wrote: > > I have a directory hierarchy of protos, like: > > dirA/a1.proto > dirA/a2.proto > > dirB/b1.proto > dirB/b2.proto > > Using protoc

[protobuf] How does this .proto file result in this generated code?

(I *believe* this question is about protocol buffers, and not gRPC, but I may be wrong.) There is a .proto file that exists as part of the Helm project: https://github.com/kubernetes/helm/blob/v2.5.0/_proto/hapi/rudder/rudder.proto As part of Helm's build process, a Go binding is generated here

[protobuf] Google ASSISTANT SDK C++ doesnt compile Showing undefined reference to vtable

Hello there I am implementing google Assistant SDK in C++ Can you check my code please whats wrong #include #include #include #include #include #include #include #include //RTaudio headers //#include "RtAudio.h" //#include //#include //grpc headers #include #include #include #include

[protobuf] Re: Including C++ header files for proto file that include multiple proto files inside it..

I think its there On Friday, July 14, 2017 at 6:53:02 PM UTC+3, ali haq nawaz wrote: > > Hello there. > I have a proto file that include other proto file inside or linked to it. > Do i need to include the generated header files for those proto in my > client implementation or they are linked auto

Re: [protobuf] How does this .proto file result in this generated code?

This code is emitted by the GRPC plugin for Java. For Go, all code gen is a plugin (protoc-gen-go ) and it includes the GRPC functionality. For Java, the core protoc knows how to emit the normal generated code, but you need the right pro

Re: [protobuf] How does this .proto file result in this generated code?

On Friday, July 14, 2017 at 12:41:18 PM UTC-7, Josh Humphries wrote: > > This code is emitted by the GRPC plugin for Java. For Go, all code gen is > a plugin (protoc-gen-go > ) and it > includes the GRPC functionality. For Java, the c

Re: [protobuf] pros and cons to upgrade protobuf v3

Thanks Josh, we don't use default values, we don't use extensions and we don't use accessor methods. All our messages (C++) are using very simple native fields and embedded without messages or messages imported from other packages. You comments encouraged me even more to upgrade the v3. Correc