I recommend bytes field. If you use string, it won't accept non-utf8 character.
On Wed, Jan 11, 2017 at 2:35 PM <[email protected]> wrote: > Late answer, but I would have recommended string. Keeps it human readable > and also, I suppose, not have to be concerned with endian order. > > On Monday, May 2, 2016 at 10:27:30 AM UTC-7, Osman Ali wrote: > > Looking use a 128 bit uuid according to rfc4122. For Proto3 should use > bytes type? > > So: > > message SendIdentifier { > bytes user_uuid = 1; > } > > > -- > 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. > -- 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.
