Re: [hybi] With deflate-stream, Close frame doesn't work as an end of data marker

[[e-mail]]

Hi,

If we could apply deflate-stream only to payload, that would solve 
the problem. I was looking for reasons why entire stream has to be
compressed, and found only one here:

http://www.ietf.org/mail-archive/web/hybi/current/msg04117.html

>From layering aspects, I would prefer any compression taking place
on top of framing layer from the other way around:

   +-------------+
   | compression |
   +-------------+
   +-------------+
   | WS framing  |
   +-------------+
   +-------------+
   |     TCP     |
   +-------------+

where, current draft -05 sugggests:

   +-------------+
   | WS framing  |
   +-------------+
   +-------------+
   | compression |
   +-------------+
   +-------------+
   |     TCP     |
   +-------------+

Justifications for the former layering would be:

o  Framing is necessary because of the underlying transport
   layer is in fact 'streaming', or TCP. (TCP and WS-framing 
   are more tightly coupled)
o  WS-layer needs to buffer entire message (passed by app/JS)
   anyway.
o  Text and binary do not interleave fragments, hence there
   needs only one context for compression / decompression in
   memory.
o  Overhead (frame headers and control frames) are much smaller
   than payload of text/binary frames and negligible as to 
   compression ratio.
o  Close frame appears at the end of stream with no traling
   bytes. (Can remove requirement for TCP graceful shutdown).

Please let me know if I am missing something...

Best.
- Yutaka