Re: the scenario where multiple tabs are requesting content from the same domain name, and run into connection limits:
I don't actually see this as being a big problem. If mega-sports- center.com wants to allow me to simultaneously watch 13 sportscasts in my browser at once, they will do domain sharding (i.e. put the video streams onto different FQDNs, i.e. server213.sportscenter.com, etc.). This approach is already quite common on some of the larger sites on the Internet, which wish to have effective parallelism > 6 (usually to lower page load latency, not for parallel streaming, but the solution works for either). It's not an ideal situation, but it's a known workaround of the connection limits while avoiding overwhelming sites that don't want such large parallelism (which would happen if we just bumped up the per-domain limit). Anyone who wishes to be a big player in the streaming video space will have the resources to implement this--subdomains are cheap. (There's been some talk of having an HTTP header that servers could use to opt-into large connection limits on a per-domain basis, but I haven't heard about it recently.) Jason _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
