>From the encoding spec, it is required (or at least: recommended) to handle out-of-order fields. I guess *in part* this helps with message concatenation. I also know of at least one case where I knowingly emit fields out of order (in my implementation; not related to the core Google implementation).
Marc On 5 July 2010 12:25, Srivats P <pstav...@gmail.com> wrote: > Hi, > > From http://code.google.com/apis/protocolbuffers/docs/encoding.html > <quote> > when a message is serialized its known fields should be written > sequentially by field number, as in the provided C++, Java, and Python > serialization code > </quote> > > Like the encoded wire format, is the above guaranteed for the C++ > Serialization API (assuming no unknown fields)? > > Background: > I'm designing a file format based on protobuf. I plan to have the > first field as a fixed size file type magic value and second field as > a fixed size checksum value, followed by other fields. While opening > such a file, I'd like to match the magic value and verify the > checksum, before parsing the whole file. > > Regards, > Srivats > > -- > You received this message because you are subscribed to the Google Groups > "Protocol Buffers" group. > To post to this group, send email to proto...@googlegroups.com. > To unsubscribe from this group, send email to > protobuf+unsubscr...@googlegroups.com<protobuf%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/protobuf?hl=en. > > -- Regards, Marc -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to proto...@googlegroups.com. To unsubscribe from this group, send email to protobuf+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
