On 03/08/2016 10:47 AM, Tim Bannister wrote: >> On 8 Mar 2016, at 18:13, William A Rowe Jr <wr...@rowe-clan.net> wrote: >> If a websocket implementation is properly stacked on top of the >> core, there is no need for special-casing this interaction. It >> will be able to speak over http or https, or conceivably even over >> a single h2, or h2c stream, and will support httpready or freebind >> mechanics. > > I chose WebSocket precisely because it's a pain and will illustrate > awkward cases. WebSocket over HTTP/2 sounds like a red herring, as > normal WebSocket runs over a stream transport (TCP). In RFC 6455 it's > an upgrade, and once that upgrade has happened then HTTP is not part > of the stack any more. WebSocket Secure runs over TLS but, again, > discards HTTP after the upgrade.
Right. WebSocket is WebSocket, and isn't communicating "over" or "inside" another stream. There is only one way to create a WebSocket connection, and that's by upgrading from an HTTP/1.1 request. AFAIK, HTTP/2 + WebSocket does not exist, nor does ALPN of a "pure" WebSocket stream. --Jacob
