[
https://issues.apache.org/jira/browse/TS-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177764#comment-13177764
]
James Peach commented on TS-841:
--------------------------------
>From IRC discussion:
6:17pm] zwoop: but, not sure it should be named TSNetAcceptTLS()
[6:17pm] zwoop: because, TSNetAccept() implies that you (the plugin) own the
port
[6:17pm] zwoop: but, with NPN, you "share" it
[6:17pm] jpeach: that's an interesting point
[6:17pm] zwoop: I think we'd wants something like TSRegisterNPNHandler(contp,
npn_string);
[6:17pm] zwoop: or some such
[6:18pm] zwoop: where contp implements the SPDY statemachine (or whatever
protocol it is)
[6:18pm] jpeach: NPN implies an implementation where the server is able to
route external ports to internal named endpoints
[6:18pm] zwoop: and, it follows the same semantics as the continuation that you
would normally provide with for TSNetAccept
...
[6:29pm] jpeach: so NPN needs to be in core code
[6:29pm] jpeach: we need an internal endpoint mapper to route NPN endpoints
[6:29pm] jpeach: we need plugin API to hook it all up
> Refactor SSL code to make it possible to perform NPN negotiation without
> entering the HTTP SM
> ---------------------------------------------------------------------------------------------
>
> Key: TS-841
> URL: https://issues.apache.org/jira/browse/TS-841
> Project: Traffic Server
> Issue Type: New Feature
> Components: HTTP, SSL
> Reporter: Leif Hedstrom
> Fix For: 3.1.3
>
>
> In order to make it possible to write protocol handlers like SPDY, we need to
> negotiate NPN protocol before entering the HTTP SM.
--
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
