Can ASP.NET MVC AsyncController be used to serve a large number of concurrent maintenance requests (long polling)?

Structures such as Node.js, Tornado, and Twisted allow developers to create applications for push applications that support a large number of concurrent freeze requests (10k +). As far as I understand, they all achieve this without creating threads to serve each hanging request.

Can I use AsyncController to serve a large number of inactive concurrent requests?

If so, are there any reasonably large ASP.NET MVC websites that use this approach to create applications with a lot of polls?

+5
source share
2 answers

I recently wrote a simple chat server example with a long poll using MVC 3 Async Controllers in an excellent article by Clay Lenhart , but I did not have the opportunity to test it using connectivity.

You can use the example in deploying AppHarbor. I configured it based on the source from the BitBucket project.

In addition, more detailed information is available from my blog explaining the project .

+3
source

AsyncController is useful (compared to a regular controller) in the following situation:

, (-, ...) - -, , , BeginXXX, IOCP ( , , ), . . , IOCP, , . : , , : , . , . .

: . , , /. . .

MSDN, ASP.NET.

, , .

+6

All Articles