- From: Robert Collins <robertc@robertcollins.net>
- Date: Fri, 21 Nov 2014 21:33:03 +1300
- To: Andy Green <andy@warmcat.com>
- Cc: Yutaka Hirano <yhirano@google.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
On 21 November 2014 19:15, Andy Green <andy@warmcat.com> wrote: > Ah since the endpoints negotiated ws using HEADERS, actually we could do without a WS flag on DATA. > > The fact that it's DATA for stream ID xxx and that ID went through a ws handshake means both sides and all intermediaries present during the ws handshake can know it is ws protocol in the DATA without an explicit flag. > > So we could just use DATA for this without any modification. Peers that understand websockets can know in some streams there's a WS_FLAGS byte at the start of the DATA payload. Peers that don't understand websockets just move opaque DATA payloads around as usual and only see normal DATA semantics going on. Right, that was my point. As long as intermediaries that don't understand its websockets won't /break/ things, we don't need anything above the base framing (at least so far as I can tell). -Rob -- Robert Collins <rbtcollins@hp.com> Distinguished Technologist HP Converged Cloud
Received on Friday, 21 November 2014 08:33:30 UTC