Re: [hybi] Flow control quota

[Takeshi Yoshino <[e-mail]>]

I think use of "message" boundary is safe. So, I'd

1. remove MASK bit, (extended) payload length, masking-key (if any) from
the original frame
2. put the remaining bytes into one WebSocket message (opcode=2 as you
said) together with channel ID

On Fri, Jun 8, 2012 at 8:06 PM, Arman Djusupov <[e-mail]> wrote:

> A solution for the 2nd option:
> We need to encapsulate frame fragments into a mux message. In this case all
> mux frames would have their FIN bit set to 1 and opCode set to 2 (binary),
> so the payload of a mux frame will be transparent to all intermediaries
> that
> do not support mux.


still true


> Mux frames would retain the current format and would
> have channelID in their extension data.


Moved to the top of the encapsulating message.


>  In addition to that each mux message

that corresponds to the first fragment of the original frame would include
> the frame length,


Replaced with the encapsulating message's message length information.


> opCode, FIN flag and RSV bits of the original frame;
>

still true.


> subsequent mux frames would include only the payload of the fragment.
>
> This format would introduce an additional overhead of 16 to 72 bits per
> original frame.
>

Additional overhead will be 1 octet per original frame.