Oops; meant to press reply-all, not reply, but:
This relates to protobuf-net. The only time the Name property is used is if
you reverse-generate from code to .proto via Serializer.GetProto (or the
similar method on RuntimeTypeModel).
On 23 May 2014 13:23, Sam Eaton nuluv...@gmail.com wrote:
I'm a big fan of Jinja2, which is a template engine. You would write a
jinja template, and then write a Python to generate the fields like you
want, pass it to the template to create the proto file for you.
Jared
On Friday, May 23, 2014 1:14:32 AM UTC-7, Ambrish Rawat wrote:
I have been
Hi
I'm new in protobuf and would need it to store different values in an
binary file.
I am using Qt 5.3 as development Environment.
My problem is to access and store the values inside the message “Cat” and
“Dog”
I think that storing the data is working right because I am able to
Hello,
I'd like to see if any prior work has been done in customizing protobuf
compilation to support message encoding/decoding against a legacy wire
format.
Put another way, I'm interested in:
1. specifying an existing protocol using protobuf's .proto file syntax, and
2. reusing protobuf's
polymorphism with nested extensions (Qt/c++)
Hi
I'm new in protobuf and would need it to store different values in an
binary file.
I am using Qt 5.3 as development Environment.
My problem is to access and store the values inside the messages “Cat” and
“Dog”
I think that storing the
Hey, guys,
After download the new protobuf 2.5.0 version, i saw a lazy option in
descriptor.proto, is it an already-implemented feature or just an in-plan
feature? cause i didn't see it mentioned in release notes.
it will be amazing if protobuf have this new feature!
Thanks in
On Mon, May 26, 2014 at 12:17 AM, Yuexuan Chen moonspirit.c...@gmail.comwrote:
Hey, guys,
After download the new protobuf 2.5.0 version, i saw a lazy option in
descriptor.proto, is it an already-implemented feature or just an in-plan
feature?
It's already implemented in our internal
There are two ways to support custom wire format with protobufs.
1. Implement the parsing/serializing code as a runtime library. The text
format support in protobuf can be seen as such a library. Support for
Json/XML is also done using this approach. It relies on the protobuf
reflection support
On Mon, May 26, 2014 at 6:56 PM, Chris Beams ch...@beams.io wrote:
Hello,
I'd like to see if any prior work has been done in customizing protobuf
compilation to support message encoding/decoding against a legacy wire
format.
Put another way, I'm interested in:
1. specifying an existing
