Summary


It is always wise to think twice before introducing asynchrony into your applications, as it makes it much more difficult to predict how your application will behave and can easily introduce difficult-to-track-down bugs. However, with ASP.NET 2.0's asynchronous task and page support, the details of managing secondary threads are mostly hidden from the developer, and the advantages of spawning work onto different threads are still gained.

The two primary reasons for using asynchronous tasks and pages in ASP.NET 2.0 are to leverage potential parallelism of concurrent I/O-bound calls in the context of a single page, and to relieve thread-pool pressure for long-running requests that are I/O-bound. If your Web application suffers from long-running pages and what seems like arbitrarily slow pages that should be very fast, you should feel comfortable introducing asynchronous operations using these asynchronous pages and tasks, without having to worry too much about managing all of the details usually encountered with multithreaded programming.




Essential ASP. NET 2.0
Essential ASP.NET 2.0
ISBN: 0321237706
EAN: 2147483647
Year: 2006
Pages: 104

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net