I saw a pretty good suggestion in this issue thread: Provide support for UUID type (a.k.a. GUID) #2224 <https://github.com/protocolbuffers/protobuf/issues/2224> @*gmabey <https://github.com/gmabey> *suggested to make use of the layout presented in RFC4122 section 4.1.2, @*billpoole-mi <https://github.com/billpoole-mi> *then further expanded upon that idea by providing a possible implementation <https://github.com/protocolbuffers/protobuf/issues/2224#issuecomment-756065336> for that approach. On Thursday, 12 January 2017 at 00:06:53 UTC+1 Bo Yang wrote:
> 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 view this discussion on the web visit https://groups.google.com/d/msgid/protobuf/ed15d978-9ce0-405f-b40a-6f3572e72a35n%40googlegroups.com.
