Thank you That is useful. I thought that there is an official specification.
On Tuesday, January 9, 2018 at 9:24:19 AM UTC-8, Josh Humphries wrote: > > This describes the basic encoding of protobuf messages into bytes: > https://developers.google.com/protocol-buffers/docs/encoding > > The format does not include a length header. If you have data that > concatenates protobuf messages, then each such message will typically be > prefixed by a varint-encoded length, to delimit multiple messages in a > single stream. (Though other usages of proto, such as gRPC, have different > framing mechanisms for concatenating multiple messages in a single stream.) > > > ---- > *Josh Humphries* > [email protected] <javascript:> > > On Tue, Jan 9, 2018 at 12:01 PM, Sergei Gnezdov <[email protected] > <javascript:>> wrote: > >> I see a user level spec but I don't see a spec that defines a binary >> format. >> >> >> Thank you >> >> -- >> 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 [email protected] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> Visit this group at https://groups.google.com/group/protobuf. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
