[
https://issues.apache.org/jira/browse/TS-4518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348621#comment-15348621
]
ASF GitHub Bot commented on TS-4518:
------------------------------------
Github user jpeach commented on a diff in the pull request:
https://github.com/apache/trafficserver/pull/736#discussion_r68462180
--- Diff: lib/ts/apidefs.h.in ---
@@ -1125,6 +1173,20 @@ extern tsapi const char *const
TS_NPN_PROTOCOL_GROUP_SPDY;
*/
extern tsapi const TSMLoc TS_NULL_MLOC;
+/*
--------------------------------------------------------------------------
+ Interface for the UUID APIs. https://www.ietf.org/rfc/rfc4122.txt. */
+typedef enum {
+ TS_UUID_UNDEFINED = 0,
+ TS_UUID_V1 = 1,
+ TS_UUID_V2,
+ TS_UUID_V3,
+ TS_UUID_V4, /* At this point, this is the only implemented version (or
variant) */
+ TS_UUID_V5,
+} TSUuidVersion;
+
+#define TSUuidStringLen 36
--- End diff --
This should be ``TS_UUID_STRING_LEN`` to be consistent with
``TS_MAX_USER_NAME_LEN``, which is the only precedent I could find :)
> UUID and HttpSM ID APIs and Machine support for a process UUID
> --------------------------------------------------------------
>
> Key: TS-4518
> URL: https://issues.apache.org/jira/browse/TS-4518
> Project: Traffic Server
> Issue Type: New Feature
> Components: Core, TS API
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 7.0.0
>
>
> As was discussed on https://github.com/apache/trafficserver/pull/199, I've
> started the work to generalize this, and breaking it up in various parts.
> This first Jira is about adding four things:
> 1) An internal process UUID, which goes into Machine. It's accessible from
> the core.
> 2) An API to get this Machine UUID.
> 3) A set of generic UUID APIs, to do things like stringification, Copy() etc.
> 4) A very simple API that exposes the HttpSM's sequences number (sm_id).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
