Re: [hybi] Frame size

On Fri, Apr 16, 2010 at 5:38 AM, Greg Wilkins <gregw@webtide.com> wrote:

>
>
> I thought one of the key arguments for a limited frame size,
> is that we could avoid the need to consider end points that
> could not store an entire frame in a buffer at once.
>

Why would you need to do that?

>
> So 2 byte's can still result in a 64k maximum frame size that
> some devices might baulk at... but not many.
>

"not many" probably isn't good enough. For the protocol to be a success it
needs to work reliably. For clients/servers, that implies that they should
be able to start processing before the entire frame has been received. For
proxies you just stream the data.. unes you're doing multiplexing for
people, in which case you have other concerns.

-=R

>
> However, if frame sizes were 4 bytes or more, then we have the
> issue that all end points will have a restriction of frame size
> that can be held in a buffer that is smaller than the maximal.
> We then need error handling for when a frame that is too large
> is offered etc.
>
> So if we are going to limit it, then is should be small
> enough so we can say that all websocket endpoints must
> be able to accept a minimal frame.
>
> In fact, I would argue for a 16k max frame size with 2
> bits given over to help with partitioning and aggregation,
> but with no requirement that an endpoint can handle
> aggregation and partitioning (unless they indicate they
> can in the handshake).
>
> cheers
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> hybi mailing list
> hybi@ietf.org
> https://www.ietf.org/mailman/listinfo/hybi
>