3 ms·
Working around browsers' maximum concurrent connections settings is a major reason to use multiple hosts. This table of browser [0] is somewhat dated but these
by extra88 11y ago
Working around browsers' maximum concurrent connections settings is a major reason to use multiple hosts. This table of browser [0] is somewhat dated but these limitations have been have always been present since the first browsers, I doubt they've radically changed in the last few years.
[0] http://sgdev-blog.blogspot.com/2014/01/maximum-concurrent-connection-to-same.html http://sgdev-blog.blogspot.com/2014/01/maximum-concurrent-co...
- pdkl95 11y agoI could have outdated information; in either case speed isn't as important as security. Why haven't servers started advertising how many connections they are willing to accept? The need for other domains could be easily removed with something like an HTTP response header: 200 Ok ... X-Max-Parallel-Connection: 10 ... This type of header could even be used to give per-page values: X-Max-Parallel-Connection: 20, scope=local-page-only (there's probably a better way to phrase these, but that works as an example) Yes, I know these are not supported by browsers yet, but sensibility is one of the best features of HTTP.
- icebraining 11y agoThat's been kinda pre-empted by HTTP2, with its TCP multiplexing and server pushing.