- From: Loïc Hoguin <essen@ninenines.eu>
- Date: Fri, 28 Oct 2016 20:55:34 +0300
- To: Costin Manolache <costin@gmail.com>
- Cc: Takeshi Yoshino <tyoshino@google.com>, Wenbo Zhu <wenboz@google.com>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
On 10/28/2016 08:41 PM, Costin Manolache wrote: > Current overhead is 2 bytes if frame is up to 125 bytes long - which I > think it's not very common, > 4 bytes for up to 64k, and 10 bytes for anything larger. > IMHO adding one byte - i.e. making it fixed 5-byte, with first as is, > and next 4 fixed length would > be easiest to parse. Is making it easy (or easier) to parse even a concern anymore? Considering the number of agents and servers already supporting Websocket, the numerous libraries for nearly all languages and the great autobahntestsuite project validating it all, reusing the existing code is a very sensible solution. > There are obviously too many options to encode and each has benefits - > my only concern was > that the choice of 1, 2, 8 bytes for length may not match common sizes. > > ( in webpush frames will be <4k ). -- Loïc Hoguin https://ninenines.eu
Received on Friday, 28 October 2016 17:56:11 UTC