It is said that IIS is not recommended for Comet programming. If that is true, how is it that other web servers are able to handle this vis a vis IIS. So what is it that other web servers do additionally which allows them to scale out.
相关问题
- How to make a .svc file write to asp.net Trace.axd
- How to deploy python flask application in conda ba
- ASP.NET won't compile to debug
- Web server farms with IIS ? Basic Infos [closed]
- how do i manually configure a virtual directory in
相关文章
- 请教IIS URL重定向的问题
- 一个愚昧的问题,在一台电脑/云服务器下,假设某个系统访问量大,给他在IIS部署多个同样的网站和部署一
- .Net5 程序发布到IIS10
- 程序是如何接收并启动监听 IIS 站点设置的端口号的?
- IIS App Pools & Static Classes
- ASP.NET code to detect whether IIS “Windows Authen
- Installing Web Deploy on IIS 7+ with Shared Config
- ASP.NET is not authorized to access the requested
We have moved away from using IIS to using a custom web server built using HttpListener. IIS imposes resource limits and screws up debugging any other ASP.NET web application you have. Running it on a different App Domain minimizes but does not resolve the problem.
A Comet connection means an HTTP connection between the server and the client (the Web page itself) which is left open for a longer time period. The server needs to have the following capabilities set up correctly:
The easiest way is to use a JavaScript framework with built-in support for Comet. See the framework's manual for more instructions on how to configure various Web servers (like IIS) correctly for Comet.
For some reason, this myth is still around. It's certainly possibly to do this with IIS, as demonstrated in our IIS-based comet server, WebSync.
The myth started with standard ASPX pages (which, if you hold open, will crap out around maybe 100 or so requests tops). It got better with async pages and handlers (which idle using much lower memory and virtually no CPU), and, with some clever working, can scale as well as, if not better than, many other comet solutions.
I'd also suggest checking out aspcomet.googlecode.com - open source and runs in IIS.