Hello all:
You know that ASP.NET Web App is truly multi-thread environment, so——
1) Is IIS or ASP.NET appliation creating each thread from ThreadPool for every request user?
2) Suppose I've limitted the MAX length for the application pool (10), and there are 11 users requesting, so there must be 1 user waiting and he/she will re-use some thread that is available for him/her? (what I mean is: suppose from 1 to 10, the thread
poor has created 1 to 10's threads, and the 11th user has to wait until someone's thread is free, and the thread pool won't create the thread again and directly use the free one?)
3) Is it possible to use a static varible with attribute "ThreadStatic" in ASP.NET environment as a "locker" to protect "thread safe"? I saw some one wrote "ThreadStatic" onto a static variable that is used for db's CRUD controls, Is it safe?
Any suggestions?
Many thanks!
Go to the complete details ...