Last post Apr 27, 2007 10:29 AM by vadivelkumar
Apr 24, 2007 11:36 AM|GAD|LINK
A short while back ago I came across an excellent article by Jeff Prosise (http://msdn.microsoft.com/msdnmag/issues/07/03/WickedCode/). The article
basically talks about asp.net asynchronous pages. An excerpt from the article is as follows:
"When the request arrives, it's assigned a thread by ASP.NET. The request begins processing on that thread, but when the time comes to hit the database, the request launches an asynchronous ADO.NET query and returns the thread to the thread pool. When the
query completes, ADO.NET calls back to ASP.NET, and ASP.NET grabs another thread from the thread pool and resumes processing the request."
What I'm really interested in knowing is how is it that ASP.NET delays page processing until any registered async operations complete? In other words, the process of returning the executing thread back to the pool, delaying the client request until the async
operations complete, notification that the async operations have completed, and then finally grabbing another thread from the pool to resume processing, how is this all accomplished? Anyone have any ideas?
Apr 24, 2007 03:29 PM|bitmask|LINK
It's using some of the Asynch design patterns in .NET: delegates, callbacks, and the IAsyncResult interface:
Apr 27, 2007 10:29 AM|vadivelkumar|LINK