Re: HTTP/2 and Websockets

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 26/11/2014 2:43 p.m., Andy Green wrote:
> 
> 
> On 26 November 2014 09:39:37 GMT+08:00, Yutaka Hirano wrote:
>> Sorry that the proposal was updated in another place: 
>> https://github.com/yutakahirano/ws-over-http2/blob/master/ws-over-http2-message-mapping.md
>>
>> 
I forgot to link the document.
>> 
>> In the github document, a WS message is encoded to HEADERS +
>> DATAs.
> 
> OK... then I guess we could agree, calling it super inefficient was
> being kind ^^
> 
> What we're talking about now, HEADERS to make the upgrade one time
> and then pure DATA representing one ws frame, would be perfect.
> But I don't know how to get rid of the WS_FLAGS byte in the payload
> right now to get there.
> 

andy, why are you still talking about "upgrade" ?
 moving the entire underlying protocol connection from HTTP/1 to WS
was a HTTP/1 artifact that should no longer be necessary at all in
HTTP/2. Just open a new WS-type stream to a peer advertising WS
support and presto it contains WS protocol.

Amos

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUdZd6AAoJELJo5wb/XPRjyIsIAKeF/vNn/i3bzWSCtnbUu5Rb
wx7RuzWsbYfRaXWXjjPxtdfNAT1uNHuL10gaoznD+GVBatJtQp2AeaBo0zqpLHob
oNIFqHNMQ1AJOdFIWfVv4LRcvefMTFDGXk1WOjtV7sw0DrQFiKTJY47/cKTYwzCO
IgTpXqjjTsNcHbRiSh2UXOVsn7q9aoQsdHy6bIfTbc9+8OATjK62VauDtczKKJtt
dL3pjs7dFePpCd3taw9apf9QoQynNh+DoIPHXXCDo1IkPdyXnHq+wcUF7iA9q+9T
/vetWnSEEAjkmmuobxjO5rjTEMGhJDQ6ARV6PjfFuH+P5l9Gsb9pVdTsuiEHjc8=
=oK+7
-----END PGP SIGNATURE-----

Received on Wednesday, 26 November 2014 09:04:46 UTC