2 ms·
That can also be an advantage, if the connection has a high throughput but a high latency (e.g. cellular networks, still), you'd much rather fetch everything in
by masklinn 8y ago
That can also be an advantage, if the connection has a high throughput but a high latency (e.g. cellular networks, still), you'd much rather fetch everything in a single request. There's a slight inefficiency in the inability to independently cache assets, but even that's not necessarily a big issue: you'd mostly inline small assets.
- TheCycoONE 8y agoYou can bump that scenario down a layer to http2 push and get the best of both worlds.
- skohan 8y agoIt still feels like a hack to work around a problem that should be solved at the protocol level. There's no technical reason that multiple assets couldn't be streamed over a single TCP connection. If it's a common use-case that a number of assets need to be loaded at once to display a web page, then this should be supported by HTTP.
- jenscow 8y agoGreat idea. Let's call it HTTP/2. https://en.wikipedia.org/wiki/HTTP/2 https://en.wikipedia.org/wiki/HTTP/2