You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Yunkai Zhang (JIRA)" <ji...@apache.org> on 2014/04/27 09:16:15 UTC
[jira] [Assigned] (TS-2760) Add TSFetchClientProtoStackSet/Get()
API in experimental.h
[ https://issues.apache.org/jira/browse/TS-2760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yunkai Zhang reassigned TS-2760:
--------------------------------
Assignee: Yunkai Zhang
> Add TSFetchClientProtoStackSet/Get() API in experimental.h
> ----------------------------------------------------------
>
> Key: TS-2760
> URL: https://issues.apache.org/jira/browse/TS-2760
> Project: Traffic Server
> Issue Type: Bug
> Components: TS API
> Reporter: Yunkai Zhang
> Assignee: Yunkai Zhang
>
> Users need a way to set/get client protocol stack when working with TSFetchSM extended API, I'll add two API showed as flow:
> {code}
> /*
> * Set client protocol stack in FetchSM
> *
> * @param fetch_sm: returned value of TSFetchCreate().
> * @param proto_stack: client protocol stack.
> */
> tsapi void TSFetchClientProtoStackSet(TSFetchSM fetch_sm, TSProtoType proto_stack);
> /*
> * Get client protocol stack in FetchSM
> *
> * @param fetch_sm: returned value of TSFetchCreate().
> *
> * return the client protocol stack of fetch_sm.
> */
> tsapi TSProtoType TSFetchClientProtoStackGet(TSFetchSM fetch_sm);
> {code}
> SPDY in core need these API to add "TS_PROTO_SPDY" to the protocol stack, so that logging module can record protocol stack correctly.
> Actually, these two API had been implemented in Taobao's branch, I forgot to migrate them to ATS core, all it's my wrong.
--
This message was sent by Atlassian JIRA
(v6.2#6252)