Re: [hybi] Review of draft-ietf-hybi-thewebsocketprotocol-13

[Iñaki Baz Castillo <[e-mail]>]

2011/9/2 Richard L. Barnes <[e-mail]>:
> Section 5.6, "Note that a particular text frame might include a partial UTF-8 sequence, however the whole message MUST contain valid UTF-8"
> This requirement is meaningless, since the concept of a "message" is not defined here.  Suggest going back to a requirement that a frame MUST contain valid UTF-8 (i.e., that it breaks at code-point boundaries).

No please. This has been already discussed.

Imagine I must send a very big WS UTF-8 message and due to max frame
size requeriments (still to know how such requiremente is
"negotiated") I need to split it in N frames. This feature would work
at the very transport core layer.

Probably I have a function that splits the whole WS message into
chunks of N bytes (I mean "bytes" because I do know the max frame size
in *bytes*), so such function just counts N bytes from the WS message
and generates a frame. Please don't force such function to be
Unicode/UTF-8 aware, no please.

-- 
Iñaki Baz Castillo
<[e-mail]>