[
https://issues.apache.org/jira/browse/TS-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yunkai Zhang updated TS-2612:
-----------------------------
Attachment: (was:
0004-TS-2612-Indroduce-TSHttpConnectWithProtoStack-API.patch)
> Introduce TSHttpConnectWithProtoStack() API
> -------------------------------------------
>
> Key: TS-2612
> URL: https://issues.apache.org/jira/browse/TS-2612
> Project: Traffic Server
> Issue Type: New Feature
> Components: TS API
> Reporter: Yunkai Zhang
> Assignee: Yunkai Zhang
> Labels: api-addition, review
> Fix For: 5.0.0
>
> Attachments:
> 0004-TS-2612-Indroduce-TSHttpConnectWithProtoStack-API.patch
>
>
> This ticket was split from SPDY ticket(TS-2431), and it based on extended
> FetchSM ticket(TS-1062);
> For some plugins that using TSHttpConnect() API to do request, the Logging
> module can't know which protocol type is used, so I add a new API:
> {code}
> tsapi TSVConn TSHttpConnectWithProtoStack(struct sockaddr const* addr,
> TSClientProtoStack proto_stack);
> {code}
> After introducing TSHttpConnectWithProtoStack() API, TSHttpConnect() API
> would be a special case of it:
> {code}
> TSVConn
> TSHttpConnect(sockaddr const* addr)
> {
> return TSHttpConnectWithProtoStack(addr, TS_PROTO_HTTP);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
