I never understood that argument. The reason you can have nice text based formats is that it will all be compressed by the server anyway, or am I missing something?
back
3 comments
No. The reason people use text based formats is so that they could be read by humans without additional tools. Compression reduces the size but it's not reasonable to claim it works better then a binary format designed for light footprint.
Joe also made a funny comment on that if you listen to his talk. He said how "People say ASCII is good because you can see what's on the wire. Well can they see electrons bouncing up and down the wire? They see what a program chooses to let them see"
Thats what I meant, sorry if the wording was poor.
But even then you're left with compressed text. If you're concerned about the amount of data you're sending on the bit level, then you're throwin all that out the second you start pumping out JSON.
Spoiler alert: servers don't do that, and even if they did, the clients would have to do it too to save bandwidth.
Content-encoding: gzip
This is not applicable to WebSockets.
Yeah, websockets have their own method: http://stackoverflow.com/questions/19298651/how-does-websock.... Cowboy already supports x-webkit-deflate-frame, will support more soon.