Does sending a message to a websocket really use 250 bytes of bandwidth for websocket stuff? Seems to in my tests..
Annoying ... I've relentlessly whittled my protocol down to 75 byte packets from 170+ using some fairly serious hackery. And now all this additional overhead!
Christopher Allan Webber likes this.
Really annoying thing is, I'm only using http because of port blocking. We can tunnel anything over http websockets, which makes port blocking irrelevant, at a cost of many extra bytes. And of course that reduces pressure for ISPs to not block ports. Progress.