You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (Commented) (JIRA)" <ji...@apache.org> on 2012/02/07 00:15:00 UTC

[jira] [Commented] (TS-961) Extend TS API to support TSNetAccept with inbound transparency

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

James Peach commented on TS-961:
--------------------------------

Hey Alan,

I was thinking about this in the context of allowing a plugin to listen on a SSL port. The approach that I'm thinking of is to add a new TSPortDescriptor API. An opaque port descriptor can be created from the string (of the form that you added recently). The descriptor can then be listened on.

Something like this:

    TSPortDescriptor TSPortDescriptorParse(const char *);
    void TSDestroyPortDescriptor(TSPortDescriptor);
    TSAction TSPortDescriptorAccept(TSPortDescriptor);

What do you think?
                
> Extend TS API to support TSNetAccept with inbound transparency
> --------------------------------------------------------------
>
>                 Key: TS-961
>                 URL: https://issues.apache.org/jira/browse/TS-961
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: TS API
>            Reporter: Yossi Gottlieb
>            Assignee: Alan M. Carroll
>            Priority: Minor
>             Fix For: 3.1.3
>
>         Attachments: api_transparency.diff
>
>
> This is required for protocol plugins to use this capability.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira