You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2014/03/12 23:46:45 UTC

[jira] [Commented] (TS-2598) Expose HttpDebugNames to public plugin APIs

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

Leif Hedstrom commented on TS-2598:
-----------------------------------

Latest proposal is:

{code}
tsapi const char* TSHttpServerStateNameLookup(TSServerState state);
tsapi const char* TSHttpHookNameLookup(TSHttpHookID hook);
tsapi const char* TSHttpEventNameLookup(TSEvent event);
{code}


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