彗星的兼容性与当前的技术 [英] Compatibility of Comet with current technology

问题描述

我听说，我可以使用 的彗星作为服务器推送技术，以及我的Ajax code提高我的web应用程序的性能。

I hear that I can use Comet as a server push technology along with my Ajax code to increase the performance of my web applications.

如何成熟，这颗彗星的技术？

How mature this Comet technology?

这是所有Web服务器的支持，编程语言和浏览器？

Is it supported by all web servers, programming languages and browsers?

什么是使用的缺点彗星？

What are the disadvantages of using Comet?

推荐答案

这是成熟的，但我想你应该考虑更多的是技术，不是一个技术了。

It is mature, though I think you should consider it more of a technique than a technology.

所有的web服务器都支持它，据我所知，虽然你将需要研究和配置特定的Web服务器，如果你正在建设一个彗星应用程序的资源的要求是有点不同。具体而言，将有更同时打开连接到服务器。在编程语言支持方面，如果你选择的服务器端语言有任何种类的阻塞或等待机制，可以支持服务器推送。所有的浏览器都支持它，以及，从浏览器的角度看，这很简单，就是需要很长的时间返回一个HTTP（S）连接。

All web servers support it as far as I know, though you will need to research and configure your particular web server if you are building a comet application as the demands on the resources are a bit different. Specifically, there will be far more simultaneous open connections to your server. In terms of programming language support, if your server language of choice has any sort of blocking or waiting mechanism, you can support server-push. All browsers support it as well, as from the perspective of a browser, this is simply an http(s) connection that takes a long time to return.

有几个缺点，在浏览器的世界，最大的可能是一个事实，即一些浏览器限制打开的连接数到特定的URL为两个。所以，如果你有一台服务器阻塞连接打开等待一些数据的推动，你是下降到只有一个连接可用于浏览器从服务器获取数据。这可以用s $ P $在一些二级域名pading你的资源来缓解，使浏览器打开更多的连接。

There are a couple of disadvantages, in the browser world, the biggest is probably the fact that some browsers limit the number of open connections to a specific URL to two. So if you have a server blocking connection open waiting for some pushed data, you are down to only one connection available for the browser to get data from the server. This can be mitigated by spreading your resources over a few second level domains to allow the browser to open more connections.

这篇关于彗星的兼容性与当前的技术的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！