asynchronous pages
- by lockedscope
I have just read the multi-threading and custom threading in asp.net articles.
http://www.williablog.net/williablog/post/2008/12/16/Custom-Threading-in-ASPNET.aspx
http://www.williablog.net/williablog/post/2008/12/16/Multi-Threading-in-ASPNET.aspx
I have couple of questions.
What does he mean by returning a thread to the pool? Is that thread completely removed from memory or put in to a state that it does not scheduled to CPU(is it in sleep state or whatever)?
If that thread is removed from memory how could it survive after async point? How this mechanism works? Are every objects(pages class, request,response etc.) are copied to somewhere else before they are disposed? (Or, is it just waiting in a sleep state and then its waked when async call ends?)
He is saying that;
"Having said that, making pages asynchronous is not really about improving performance, it is about improving scalability"
then he is saying;
"I'm sorry to say that it will do nothing for scalability or performance."
So which one is true? or for which case(s) are they true?
