On Tue, Sep 06, 2011 at 10:43:38AM -0400, Richard L. Barnes wrote:
> Clearly it already has to be WebSocket aware, and it already has to read the
> opcode in order to distinguish data frames from control frames. Adding on a
> requirement to break at code point boundaries does not seem hugely one
On Tue, Sep 06, 2011 at 10:51:10AM -0400, Richard L. Barnes wrote:
> No, you have to process at most three bytes, four if you include the opcode.
> See sample code.
> --Richard
I think you misunderstood me. When you receive 40kB of UTF-8 text, if
you want to stop on frame boundaries, you have t
On Thu, May 07, 2020 at 06:47:15AM +, Poul-Henning Kamp wrote:
>
> In message <977f061c-a4bb-413b-b26c-51c7a694f...@mnot.net>, Mark Nottingham
> writes:
>
> >Perhaps in full context:
> >
> >~~~
> >For example:
> >
> > Example-ScaledInt: 4503; suffix=3DM
> >
> >Could be used to indic
