4 ms·
"a few headers" if 50% of your payload is headers, thats a big deal. Mind you XMPP isn't all that efficient either. as its all based on XML.
by KaiserPro 8y ago
"a few headers" if 50% of your payload is headers, thats a big deal.
Mind you XMPP isn't all that efficient either. as its all based on XML.
- edhelas 8y agoI'm inviting you to read this page https://xmpp.org/about/myths.html https://xmpp.org/about/myths.html :)
- KaiserPro 8y agoI didn't say slow, I said efficient. Its hilariously verbose compared to a decent binary protocol. Failing that something based on protobuffers. In the embedded world a JSON/XML parser eats a tonne of resources. One could of course use it over satcomm as it says, but its hilariously expensive when you are paying by the byte. But, compared to a massive JSON goop with embedded pictures that twitter uses, its a paragon of speed.
- icebraining 8y agoThe request and response headers for this HN page were 676 and 591 bytes, respectively, and the biggest ones (e.g. Content-Security-Policy, X-XSS-Protection) are specific to web browsers. For the kind of content sent over WebSub (generally an Atom or RSS feed with one or more long messages), it's much less than 50%.