Hi, On Tue, Jun 14, 2016 at 2:36 PM, Simone Bordet <simone.bor...@gmail.com> wrote: > That is again a semantic problem, but I think this one is simple: the > implementation cannot guarantee that one API call correspond to one > frame. > There are, for example, fragmentation extensions that > fragment/reassemble frames into smaller/larger units, so it that > extension is in place the guarantee is lost. > Same for gzipping. I know that the current draft does not support > extensions, but a 1-to-1 semantic is not something you want to bind to > when in future you may add extensions.
To add on this, Joakim noted that when/if WebSocket is transported by HTTP/2, the frame size will likely be bound to the HTTP/2 frame size (default 16 KiB), so the possibly enormous WebSocket frames will be fragmented. Thanks ! -- Simone Bordet http://bordet.blogspot.com --- Finally, no matter how good the architecture and design are, to deliver bug-free software with optimal performance and reliability, the implementation technique must be flawless. Victoria Livschitz
