Re: encoding of embedded messages and repeated elements

2009-06-25 Thread Kenton Varda
Yes, groups are never going to fully go away. But we recommend against using them in new code. On Thu, Jun 25, 2009 at 9:13 AM, Piotr Findeisen piotr.findei...@gmail.comwrote: Hi! On Jun 24, 8:42 pm, Kenton Varda ken...@google.com wrote: The end-tag approach is more efficient than your

Re: encoding of embedded messages and repeated elements

2009-06-24 Thread etorri
Does some existing parser actually implement that skipping feature? There would not be any need for a end-tag. Let's assume that there would be two different tags 2 - Length_Delimited, which could contain a packed list of bytes (string, memory block) or other types where the parser needs to

encoding of embedded messages and repeated elements

2009-06-23 Thread etorri
Hello, The length delimited encoding basically tells that the following N bytes belong to this field. Wouldn't it be easier to instead use the number of elements that belong to the embedded message (repeated element). Now (as far as I have understood) the message needs to be built from

Re: encoding of embedded messages and repeated elements

2009-06-23 Thread Kenton Varda
The advantage of writing the length is that a parser can skip the entire sub-message easily without having to parse its contents. Otherwise, we would probably use the group encoding for sub-messages, where a special end tag marks the end of the message. On Tue, Jun 23, 2009 at 9:06 AM, etorri