You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In an ASP.NET application there are a limited number of request threads available. When request threads are all used up, then any future requests will be denied (i.e. a DOS attack). A way to mitigate this is to release a thread while I/O operations are occurring allowing re-use of the thread & push an operation back onto the thread pool when the I/O operation completes.
This can be re-used in the synchronous calls to prevent repetitious code and to prevent build breaks by using the Result property (though, don't use this in the async methods since it blocks a thread).
In an ASP.NET application there are a limited number of request threads available. When request threads are all used up, then any future requests will be denied (i.e. a DOS attack). A way to mitigate this is to release a thread while I/O operations are occurring allowing re-use of the thread & push an operation back onto the thread pool when the I/O operation completes.
For example, instead of...
... use the async await pattern to allow other requests to re-use the threads while awaiting IO requests...
This can be re-used in the synchronous calls to prevent repetitious code and to prevent build breaks by using the Result property (though, don't use this in the async methods since it blocks a thread).
For more information on async\await, see http://msdn.microsoft.com/en-us/library/hh191443.aspx
The text was updated successfully, but these errors were encountered: