[
https://issues.apache.org/jira/browse/TS-2598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13936268#comment-13936268
]
ASF subversion and git services commented on TS-2598:
-----------------------------------------------------
Commit d3fd1e674b0e6d51fd3e8f4c49ed7d5d9eeb56a3 in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=d3fd1e6 ]
TS-2598 Expose HttpDebugNames to public plugin APIs
> Expose HttpDebugNames to public plugin APIs
> -------------------------------------------
>
> Key: TS-2598
> URL: https://issues.apache.org/jira/browse/TS-2598
> Project: Traffic Server
> Issue Type: New Feature
> Components: TS API
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Labels: api-addition
> Fix For: 5.0.0
>
>
> It'd be really useful to expose all the HttpDebugNames:: functions into one
> (or several?) API calls.
> Either
> {code}
> const char* TSGetDebugName(type, ID);
> {code}
> where type would be a new enum of e.g.
> typedef enum
> {
> TS_DEBUG_STATE_NAME,
> TS_DEBUG_METHOD_NAME,
> TS_DEBUG_EVENT_NAME,
> ...
> } TSDebugNameID;
> or perhaps
> {code}
> const char* TSGetDebugStateName(id);
> const char* TSGetDebugMethodName(id);
> ...
> {code}
> I personally favor the former, it's more easily extended with future
> additions.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
