2013/2/2 Oliver Jowett <>:
> Fields don't have to be encoded in any particular order, so you can have a
> valid message encoding where the encoding of 'eom' is followed by other
> fields.

I.e. I cannot be sure eom is the last field?

> I'm not sure
> whether you are asking whether this would work with the current encoding (it
> won't)

Exactly this one. I see. Thanks. I will go with standard practice and
delimit by VarInt32 before message data.

Roman Simakov

You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
To post to this group, send email to
Visit this group at
For more options, visit

Reply via email to