[protobuf] Serialized Message Field Order

2010-07-05 Thread Srivats P
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

Re: [protobuf] Serialized Message Field Order

2010-07-05 Thread Marc Gravell
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

[protobuf] Re: using the new plugin infrastructure

2010-07-05 Thread marcmo
jason, thanks for the response. for the stuff that i needed i found everything and the plugin stuff works great (i use it to generate a custom rpc implementation of the lite version that is suited for our embedded environment) insertion points where not needed so i almost forgot about that. today

[protobuf] Existing domain model

2010-07-05 Thread Pradeep Thomas
We have an existing object model in java with hibernate annotations for persistence. For client-server communication what are the pros of cons of using protocol buffers, because we do not not want to modify the existing object model or generate it again. -- You received this message because you