可以ASP.NET MVC的AsyncController用来服务大量并发请求挂的（长轮询）？ [英] Can ASP.NET MVC's AsyncController be used to service large number of concurrent hanging requests (long poll)?

问题描述

喜欢的Node.js，龙卷风，扭曲的框架让开发人员创建一个支持大量并发请求挂（10K +）的服务器的推送应用程序。据我了解，他们都通过不创建线程来为每个请求挂着实现这个。

Frameworks like Node.js, Tornado, and Twisted let developers create server-push applications that supports large number of concurrent hanging requests (10k+). From what I understand, they all achieve this by not creating threads to service each hanging request.

能否AsyncController用来服务大量非活动的并发请求？

Can AsyncController be used to service large number of inactive concurrent requests?

如果这样，是否有使用这种方法制造长轮询应用程序的任何相当大的ASP.NET MVC的网站？

If so, are there any reasonably large ASP.NET MVC websites using this approach to create long-poll applications?

推荐答案

我最近写了一个的使用基于的 MVC 3异步控制器一个长轮询聊天服务器=的简单的例子，http://clay.lenharts.net/blog/2010/10/19/websockets -is爽，但是，什么灿你-DO /今天相对=nofollow>黏土由伦哈特伟大的文章，但我还没有真正有一堆测试出来的机会连接。

I recently wrote a simple example of a Long Polling Chat Server using MVC 3 Async Controllers based on a great article by Clay Lenhart but I haven't had the chance to really test it out with a bunch of connections.

您可以使用例如在AppHarbor部署我建立了基于从到位桶项目的来源。

You can use the example on a AppHarbor deployment I set up based on the source from the BitBucket project.

另外，可以从我的博客文章解释该项目的更多信息。

这篇关于可以ASP.NET MVC的AsyncController用来服务大量并发请求挂的（长轮询）？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！