0007您的服务器可以处理多少并发连接取决于您的硬件资源。如果你有足够的内存和cpu,你应该能够处理〜100k或许更多。但是如果每个请求通过tcp / ip访问数据库或其他资源,您可以限制每个ip可用端口数(65k)。您还应该针对单独的域执行推送请求,因为浏览器通常会覆盖每个域的两个并发连接,因此您不会影响正常的网页加载。How many concurrent connections your server can handle depends on your hardware resources. If you have enough memory and cpu you should be able to handle ~100k and maybe more. But if each request access a database or some other resource over tcp/ip, you could be limited to the number of ports per ip available (65k). You should also have the push requests go against a separate domain, as a browser normally caps to two concurrent connections per domain, so you won't interfere with the normal page loading.使用轮询与缓存服务器结合使用是一个很好的解决方案。您可以在服务器上拥有每个客户端更新高速缓存的逻辑,从而减少每次轮询的负载。您可以更新已在X分钟内登录/轮询的用户的缓存,以减少缓存更新。对我来说,实施拉力比拉力更容易,技术聪明。Using polling in combination with cache servers in the front is a good solution. You can have logic on the server which updates the cache per client, reducing the load for each poll. You could update the cache for users who have signed in/polled within the X number of minutes to reduce the cache updating even more. And to me implementing pull is easier than pull, technology wise. 这篇关于从服务器端应用程序向客户端推送消息?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持! 上岸,阿里云!