[
https://issues.apache.org/jira/browse/THRIFT-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545957#comment-17545957
]
Yuxuan Wang commented on THRIFT-5587:
-------------------------------------
# +1 to uuid as that's the more "standardized" name as far as I understood.
# uuid actually has several different versions (e.g. v4 is pure 122-bit of
randomness, other versions have time/namespace/etc. builtin), do we want to
support all or only v4?
# (this is a minor concern, not really a big deal) currently the go library
has no third party dependencies, but since go stdlib does not have any uuid
library, this will force us to add a third party dependency for it.
> Introduce guid as additional builtin type
> -----------------------------------------
>
> Key: THRIFT-5587
> URL: https://issues.apache.org/jira/browse/THRIFT-5587
> Project: Thrift
> Issue Type: New Feature
> Components: Compiler (General)
> Reporter: Jens Geyer
> Assignee: Jens Geyer
> Priority: Major
>
> I hereby propose to add *{{guid}}* as an additional built-in basic type.
> *Rationale:*
> * Guids (or uuids) are a state of the art and well-understood way to
> identitify data entities.
> * There is support in next to all languages' runtimes to generate, convert
> and store such data.
> * Although conversion to and from string or binary is certainly possible, it
> is also rather cumbersome.
> * A distinct datatype enables us to sent it in the most suitable way across
> the wire: JSON=text, Compact=binary
> *Remarks*
> * I am open to discuss the term "guid" vs "uuid". Coming from NET platforms
> I would tend to guid, but I am open to uuid (or even both) as well. That's
> just a detail.
> * If no significant concern is raised, I would move on and implement C#,
> Delphi and Haxe bindings (as sub-tasks) myself and leave the rest to the
> community.
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
