On Wed, Oct 19, 2016 at 11:20 PM, Arne Goedeke <e...@laramies.com> wrote: > On 10/18/16 11:46, Stephen R. van den Berg wrote: >> Arne Goedeke wrote: >>> * permessage-deflate is activated by default. i don't believe that >>> this is a good choice. >> >> The default is what should help most users. I think it would have, but >> it's not a big deal. > > My applications for websockets usually focus on binary data. I usually > care more about latency and CPU than bandwidth and the payload does not > compress well. This is probably different for situations which involve > text. I don't know what other people do.
It'd have to be decent quantities of text. I have a D&D battle grid that could benefit from websocket support (it currently uses long polling). The messages would be text, but a single line at a time, and generally no more than 20-30 characters. Compression isn't going to materially affect those - they'll be carried in a single packet either way. +1 on sitting tight and waiting for more info. ChrisA
