blocks|key|207662|text|IE甚至更糟糕，每个域限制有2个连接。但我不会依赖于修复客户端浏览器。即使你能控制它们，像chrome这样的浏览器也会自动更新，将来发布的版本可能会与你预期的不同。我会集中精力解决您的系统设计中的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|207663|你的选择是：|207664|按顺序加载映像，以便每次只有1或2个XHR调用处于活动状态(使用来自上一个映像的成功事件来检查是否有更多的映像要下载并启动下一个请求)。|ordered-list-item|207665|使用像serverA.myphotoserver.com和serverB.myphotoserver.com这样的子域。每个子域都有自己的连接限制池。这意味着如果你愿意的话，你可以有2个请求到5个不同的子域。缺点是这些照片将根据这些子域进行缓存。顺便说一句，这些不需要是“镜像”域，您只需在同一个网站/服务器上创建额外的DNS指针即可。这意味着您不需要管理多台服务器，只需管理一台具有多个DNS记录的服务器。|207666|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|N|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|O|8|@]|9|@]|A|$]]]|J|$]]

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:

<ol>
<li>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).</li>
<li>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.</li>
</ol>

blocks|key|2265034|text|似乎没有一种外部方法可以破解可执行文件的行为。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2265035|您可以修改Chrome(ium)可执行文件，因为这些信息显然是编译在。这种方法在支持和自动升级方面带来了很多问题，所以您可能希望避免这样做。您还需要了解二进制文件的如何进行更改，这不是大多数人可以在几天内得到的东西。|offset|length|2265036|如果您编译了自己的浏览器，您将为自己创建一个支持问题，因为您被某个特定的修订版所困。如果您想获得新的特性和bug修复，您将不得不重新编译。所有这些都涉及跟踪Chrome开发中的bug和构建破坏--这不是web开发人员应该做的事情。|2265037|我现在会遵循@BenSwayne的建议，但可能值得考虑一下，在客户端(+web浏览器)之外进行一些工作，并将其置于运行在同一台或不同机器上的后台进程中。这个过程可以处理更多的连接，您只需要负责从其中获取数据。因为它是本地的(Ish)，所以即使连接最少，结果也会很快返回。|2265038|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikibooks.org/wiki/X86_Disassembly/Disassemblers_and_Decompilers^0|0|2A|6|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

There doesn't appear to be an external way to hack the behaviour of the executables. 

You could modify the Chrome(ium) executables as this information is obviously compiled in. That approach brings a lot of problems with support and automatic upgrades so you probably want to avoid doing that. You also need to understand <a href="http://en.wikibooks.org/wiki/X86_Disassembly/Disassemblers_and_Decompilers" rel="nofollow">how to make the changes</a> to the binaries which is not something most people can pick up in a few days.

If you compile your own browser you are creating a support issue for yourself as you are stuck with a specific revision. If you want to get new features and bug fixes you will have to recompile. All of this involves tracking Chrome development for bugs and build breakages - not something that a web developer should have to do.

I'd follow @BenSwayne's advice for now, but it might be worth thinking about doing some of the work outside of the client (the web browser) and putting it in a background process running on the same or different machines. This process can handle many more connections and you are just responsible for getting the data back from it. Since it is local(ish) you'll get results back quickly even with minimal connections.

blocks|key|441682|text|我不知道你是否可以在Windows之外的Chrome上这么做--一些谷歌用户显示，Chrome+(也可能是Chromium)可能会对某个注册表攻击做出很好的反应。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|441683|但是，如果您只是在不修改代码库的情况下寻找一个简单的解决方案，那么您考虑过Firefox吗？在about:config中，您可以搜索"network.http.max“，其中有几个值绝对值得一看。|441684|另外，对于一个不会移动的设备(即它被安装在一个固定的位置)，你应该考虑不要使用Wi(即使是家庭插头也是延迟/稳定/断开连接的一步)。|441685|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I don't know that you can do it in Chrome outside of Windows -- some Googling shows that Chrome (and therefore possibly Chromium) might respond well to a certain registry hack. 

However, if you're just looking for a simple solution without modifying your code base, have you considered Firefox? In the about:config you can search for "network.http.max" and there are a few values in there that are definitely worth looking at.

Also, for a device that will not be moving (i.e. it is mounted in a fixed location) you should consider not using Wi-Fi (even a Home-Plug would be a step up as far as latency / stability / dropped connections go).

blocks|key|207812|text|顺便说一下，HTTP1/1规范(RFC2616)建议每个服务器不超过2个连接。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|207813|使用持久连接的客户端应该限制它们维护到给定服务器的同时连接的数量。单用户客户端与任何服务器或代理的连接不得超过2个.一个代理应该使用最多2*N到另一个服务器或代理的连接，其中N是同时活动的用户数。这些指导方针旨在提高HTTP响应时间并避免拥塞。|blockquote|207814|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1^0|F|9|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@$A|P|B|Q|1|R]]|C|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|C|$]]|$1|G|3|-4|5|6|7|T|8|@]|9|@]|C|$]]]|H|$I|$5|J|K|L|C|$M|N]]]]

BTW, HTTP 1/1 specification <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec8.html#sec8.1" rel="nofollow noreferrer">(RFC2616)</a> suggests no more than 2 connections per server.

<blockquote>
 Clients that use persistent connections SHOULD limit the number of simultaneous connections that they maintain to a given server. A single-user client SHOULD NOT maintain more than 2 connections with any server or proxy. A proxy SHOULD use up to 2*N connections to another server or proxy, where N is the number of simultaneously active users. These guidelines are intended to improve HTTP response times and avoid congestion.
</blockquote>

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?

Increasing Google Chrome's max-connections-per-server limit to more than 6

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

据我所知，目前，2011年末，每个服务器的最大连接限制仍然是6。如果我错了，请纠正我。这是不好的，我们不能很容易地解决这个问题，就像在Firefox中一样。据我所知，这个值是硬编码的。解决方案之一是下载Chromium的源代码并重新构建它们。还有更简单的解决办法吗？有没有什么棘手的方法可以在不创建一打镜像域的情况下破解...

问将Google Chrome的最大连接-每个服务器的限制提高到6以上
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Google Chrome的最大连接-每个服务器的限制提高到6以上EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将Google Chrome的最大连接-每个服务器的限制提高到6以上
EN