This is the perfect example of what worries me about WebSockets and WebRTC, that people use it for data better served over HTTP. "But it's faster and purer, wit

This is the perfect example of what worries me about WebSockets and WebRTC, that people use it for data better served over HTTP. "But it's faster and purer, with less overhead!" I hear you say. Sure, but that overhead is very useful, guaranteeing things like on-the-fly compression, caching, data integrity, and so on. The only time you should use WebSockets/WebRTC is if you really need Real Time Communication (really, it's in the name). A real-time game doesn't care about data coming in the right order exactly, and a video call can lose a couple frames before people notice. But the web has a protocol, and it's the HyperText Transfer Protocol.