@clemensv Early days. I wouldn't put much faith in adoption by anybody who doesn't grok network effects, or why pubsub sucks for this
1
@distobj I see you're trying to guess a few elements like MQTT or pubsub. It'd be neat if things were that straightforwardly wrong.
1
@kellabyte True, but the greater the network effects, the more tolerable the inefficiencies. Compare MQTT value prop with WAP circa 1998
3
@distobj I disagree to a point. If I'm requiring high performance it makes no sense to take the hit of an inefficient protocol.
1
@kellabyte Totally agreed, but I think high perf is a tiny part of this application space
2
@distobj @kellabyte but high-scale persistent bidi connections with tiny overhead are
3
@stilkov @distobj @kellabyte "we'll multiplex all the world's TCP traffic over 443" isn't all that unlikely, but I wouldn't call that HTTP
2
@clemensv @distobj @kellabyte I agree if we're talking about something like Websocket, but HTTP/2 very much *is* HTTP
May 15, 2013 路 4:31 PM UTC