> > for servers: > > > > client mask (4 octets) > > last frame end % 4 : 2 Bits => to know where within mask to start for > unmasking the next masked frame received > > Server shouldn't need to remember this, since each fragmented frame > comes with its own masking key. At least that's how I read the spec; there's > nothing in Section 5.4 that seems to indicate that masking keys get carried > over from one fragment to another.
yep, you are right, sloppyness on my side. what I wanted to say: "=> to know where within mask to start for unmasking the next _chunk of octets_ received" it's only need with a WS implementation capable of full streaming, that is i.e. processing frames of 2^63 length. _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
