Asynchronous Controllers in ASP.NET MVC

added by Grishma Govani
4/25/2013 5:29:17 PM

0 Kicks, 54 Views

Web applications typically have a limited number of threads that are standing by to handle requests. When all threads are busy, new requests are queued until a thread becomes available. If in the process of creating a response, your MVC controllers are waiting for lengthy I/O operations to complete, it is possible that the threads aren't doing much, but are still tied up and aren't free to handle new requests. This problem commonly occurs when controllers make requests to external web services. Learn how asynchronous controllers supported by MVC can free thread can to handle other requests


0 comments