For effective service multiple client requests, WebServer respond to service requests by using multiple processes or generating multiple threads. ASP.NET does not use exception and use multiple threads in response requests in a process. Based on this status, ASP.NET developers do not need to care about multithreaded environment. The page demand response is always in a thread, and when there is a new requirement, a new page will create a completely different instance. Different instances and model components for applications are always in response to each request. However, it is very important to understand how to use threads to respond to requests.
At the beginning, ASP.NET responds to requests with a CLR thread pool. The pool is in the machine configuration file (machine.config), which is set to 25 working threads and 25 I / O threads by default.
