[ 
https://issues.apache.org/jira/browse/THRIFT-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551776#comment-17551776
 ] 

Jens Geyer commented on THRIFT-5587:
------------------------------------

{quote}Should the related PR (doc, other languages) be on the branch as 
well?{quote}

Not sure. I merged the docs into master. Probably branch would be the better 
choice, but I'm not going to revert it. 

{quote}If not I’ll try to generate some tomorrow.{quote}

The testUuid() method of the ThriftTest suite does that. The ones I implemented 
so far (e.g. netstd) send 00112233-4455-6677-8899-aabbccddeeff to test for 
proper byte ordering.

Thanks! 

> Introduce uuid 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 *{{uuid}}* as an additional built-in basic type.
> *Rationale:*
>  * Uuids (or Guids) 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)

Reply via email to