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/03/10 16:20:46 UTC

[jira] [Assigned] (TS-2612) Indroduce TSHttpConnectWithProtoType() API

     [ https://issues.apache.org/jira/browse/TS-2612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yunkai Zhang reassigned TS-2612:
--------------------------------

    Assignee: Yunkai Zhang

> Indroduce TSHttpConnectWithProtoType() 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: 0001-TS-2612-Indroduce-TSHttpConnectWithProtoType-API.patch
>
>
> This ticket was split from SPDY ticket(TS-2431).
> 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 TSHttpConnectWithProtoType(struct sockaddr const* addr, TSNetProtoType proto_type);
> {code}
> After introducing TSHttpConnectWithProtoType() API, TSHttpConnect() API would be a special case of it:
> {code}
> TSVConn
> TSHttpConnect(sockaddr const* addr)
> {
>   return TSHttpConnectWithProtoType(addr, TS_NET_PROTO_HTTP);
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)