Re: [hybi] frame length encoding

[John Tamplin <[e-mail]>]

On Sun, Aug 22, 2010 at 3:01 PM, Shelby Moore <[e-mail]> wrote:

> The point above is that some agents may choose to always set their maximum
> frame size to the size of the _SMALLEST_ size field, so that they don't
> have to do comparison tests.
>

I don't believe that is what was being suggested, and if you account for the
processing going on on the client I am sure it will be much more to process
n fragments rather than one condition in looking at the length field.


> It was reported that on this list (and further discussed in private):
>
> http://www.ietf.org/mail-archive/web/hybi/current/msg03453.html
>
> that multi-core coordination overhead may not scale proportionally with
> network bandwidth, and thus making the protocol as stateless as possible
> is very important in that case. I am not arguing that is the case. I am
> trusting the expertise of concensus. I am also saying why should we risk
> it for 2% savings in network bandwidth overhead?
>

I don't understand "stateless" in this context -- we are not talking about
maintaining state across different frames, but rather you look at one byte
and if it is a given value (or two given values in option 2) then you read
following bits for the length instead.

-- 
John A. Tamplin
Software Engineer (GWT), Google