In today’s world most of the application work based on Synchronous programming in which the client sent a request to the server and server process the request and send a response back to client.
Synchronous controllers work well for the concept but it cannot handle long-running processes.
When the user sends a request to a server then ASP.NET will provide one of the threads from the thread pool to handle the request. If the request process is taking less time to complete then
it provides faster output to the client but when the request
takes more time for the process then it will block the thread and the thread will not be available to another request to handle.
The large requests are sent from users and all are long-running processes then the server will be blocked then there will be no thread to handle this request and the server will fire Error message
“Server too Busy”. To handle this we all need to use Asynchronous Controllers in asp.net MVC.
When we Use Asynchronous Controllers
For long ¬running operations
For web¬services related operations
Join MindStick Community
You need to log in or register to vote on answers or questions.
We use cookies to ensure you have the best browsing experience on our website. By using our site, you
acknowledge that you have read and understood our
Cookie Policy &
Privacy Policy.
Asynchronous Controller in Asp.Net MVC
In today’s world most of the application work based on Synchronous programming in which the client sent a request to the server and server process the request and send a response back to client. Synchronous controllers work well for the concept but it cannot handle long-running processes.
When the user sends a request to a server then ASP.NET will provide one of the threads from the thread pool to handle the request. If the request process is taking less time to complete then it provides faster output to the client but when the request takes more time for the process then it will block the thread and the thread will not be available to another request to handle.
The large requests are sent from users and all are long-running processes then the server will be blocked then there will be no thread to handle this request and the server will fire Error message “Server too Busy”. To handle this we all need to use Asynchronous Controllers in asp.net MVC.
When we Use Asynchronous Controllers