Google Chrome的每服务器最高连接数限制增加到6个以上 [英] Increasing Google Chrome's max-connections-per-server limit to more than 6

问题描述

据我所知，在目前这个时候，2011年末，每个服务器的最大连接数限制仍然是6.如果我错了，请纠正我的错误。这很糟糕，我们无法像Firefox那样轻松解决这个问题。据我所知，这个值是硬编码的。

其中一个解决方案是下载Chromium的源代码并重建它们。有没有更简单的解决方案？

是否有任何棘手的方法来破解这个，而不创建一个镜像域？

为什么我问这个问题：我的任务是创建一个html-javascript幻灯片，它将在全屏浏览器中运行，并且巨大的显示器挂在墙上。这个javascript真的很复杂，它预先载入照片，并对我的Web服务进行了大量的Ajax调用。如果WIFI连接速度慢，如果加载6张照片，则AJAX调用失败，应用程序运行不正常。我想要一个快速的解决方案，基于http或浏览器或ubuntu调整其他东西，因为重建javascript应用程序将需要数天。

Offtopic：你知道其他任何东西可以调整我的具体情况？

解决方案

但我不会依靠修复客户端浏览器。即使你可以控制它们，像chrome这样的浏览器也会自动更新，未来的版本可能会有不同的表现。我会专注于在您的系统设计中解决问题。

您的选择是：

1. 按顺序载入图像，以便一次只能激活1或2个XHR呼叫（使用上一张图像中的成功事件来检查是否有更多图像需要下载并开始下一个请求） 。
   

2. 使用像serverA.myphotoserver.com和serverB.myphotoserver.com这样的子域名。每个子域都有自己的连接限制池。这意味着如果你愿意，你可以有2个请求去5个不同的子域。垮台是照片将根据这些子域被缓存。顺便说一句，这些不需要是镜像域，你可以制作额外的DNS指针到完全相同的网站/服务器。这意味着您不必担心管理多台服务器，只需要一台服务器拥有多个DNS记录。

As far as I know, at the current moment, late 2011 the max-connections-per-server limit remains 6. Please correct me if I am wrong. This is bad that we cannot fix this easily as in Firefox. As far as I know this value is hardcoded.

One of the solutions is to download the Chromium's sources and rebuild them. Is there a more easy solution?

Is there any tricky way to hack this without creating a dozen of mirror-domains?

Why I'm asking the question: My task is to create a html-javascript slideshow that will run inside a fullscreened browser, and a huge monitor is hanging on the wall. The javascript is really complicated, it preloads photos and makes a lot of ajax calls to my web services. If WIFI connection is slow, if 6 photos are loading, the AJAX calls fail, the application runs bad. I want a fast solution based, on http or browser or ubuntu tweak something else, because rebuilding the javascript app will take days.

Offtopic: do you know any other things that can be tweaked in my concrete situation?

解决方案

IE is even worse with 2 connection per domain limit. But I wouldn't rely on fixing client browsers. Even if you have control over them, browsers like chrome will auto update and a future release might behave differently than you expect. I'd focus on solving the problem within your system design.

Your choices are to:

1. Load the images in sequence so that only 1 or 2 XHR calls are active at a time (use the success event from the previous image to check if there are more images to download and start the next request).

2. Use sub-domains like serverA.myphotoserver.com and serverB.myphotoserver.com. Each sub domain will have its own pool for connection limits. This means you could have 2 requests going to 5 different sub-domains if you wanted to. The downfall is that the photos will be cached according to these sub-domains. BTW, these don't need to be "mirror" domains, you can just make additional DNS pointers to the exact same website/server. This means you don't have the headache of administrating many servers, just one server with many DNS records.

这篇关于Google Chrome的每服务器最高连接数限制增加到6个以上的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！