防火墙是持久 http 连接的瓶颈吗？
我正在构建一个客户端服务器应用程序，其中客户端将使用长期的http会话将数据从服务器推送到客户端（有时称为http推送、反向ajax、服务器推送、长轮询、http1.1等）。 ）
如果我可能有数千或数十万个客户端都保持与服务器环境的开放连接，那么防火墙/负载平衡器是否有通用策略来终止会话（如果它们打开时间过长）？防火墙/负载均衡器是否具有可扩展性限制，它们只能托管最大数量的开放连接（即使没有发送数据）？
我希望防火墙和负载均衡器具有 Http 1.1 的功能，以保持会话打开而不占用 cpu 和内存资源。如果不是这种情况，则防火墙是并发打开并发连接数的瓶颈。
I am building a client server application, where clients will use a long-lived http sessions to push data from the server to the client (sometimes referred to as http push, reverse ajax, server push, long-polling, http1.1 etc.)
If I have potentially thousands, or hundreds of thousands of clients all maintaining open connections to the server environment, are there common policies for firewalls/loadbalancers to terminate sessions if they are open for too long? do firewalls/loadbalancers have scalability constraints where they can only host a maximum number of open connections (even if there is no data being sent)?
I am hoping that firewalls and load balancers have features with Http 1.1 to keep sessions open without occupying cpu and memory resources. If this is not the case, then the firewall is a bottleneck for the number of concurrent open concurrent connections.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
好吧，如果您操作正确，您的 HTTP 会话不应该那么长。对于大多数使用 COMET 和 BOSH（或类似的东西）的聊天实现，连接保持打开状态的时间不会超过一两分钟（之后会发出新请求来重新建立 HTTP 连接）。
Well, if you're doing things correctly, your HTTP sessions shouldn't be all that long. With most chat implementations using COMET and BOSH (or something similar), the connections aren't held open for longer than a minute or two (after which a new request is made to re-establish the HTTP connection).