You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jens Geyer (Jira)" <ji...@apache.org> on 2022/06/03 07:11:00 UTC

[jira] [Updated] (THRIFT-5587) Introduce guid as additional builtin type

     [ https://issues.apache.org/jira/browse/THRIFT-5587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jens Geyer updated THRIFT-5587:
-------------------------------
    Description: 
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.

 

  was:
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 oopen to uuid (or even both) as well. That's just a detail.
 * If no sinbificant concern is raised, I would move on and implement C#, Delphi and Haxe bindings (as sub-tasks) and leave the rest to the community.

 


> 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)