|
 |
|
 |
 |
Create a Custom IHttpHandler to Allow ASP.NET Pages to Communicate with Each Other
|
by Andy Elmhorst
Sales Rank: 4970131
|
List Price: $8.00
$8.00
At Amazon
|
|
Do you have the free reader for this item?
|
Format: Adobe Reader PDFPrintable: Yes. This title is printableMac OS Compatible: OS 9.x or laterWindows Compatible: YesHandheld Compatible: Yes. Adobe Reader is available for PalmOS, Pocket PC, and Symbian OS.
File Size: 132 KB
Digital: 11 pages
Book Description
One of the questions that experienced web developers typically ask when learning the ASP.NET framework is this: When I want to transfer control to a new page from the current page, how do I create an instance of the next page and pass it the state of the current request? To accomplish this, the default mechanism provided by the ASP.NET framework is to redirect the browser to the next page using the Page.Navigate() method. This approach to page navigation can be the cause of numerous undocumented dependencies between ASP.NET pages, their possible query string arguments and items stored in the Session. It also does not allow type checking to be done at compile time on the state information passed between the pages. In this article, Andy Elmhorst shows us that it is possible for ASP.NET pages to communicate elegantly with each other as real objects. In the process, the application will save a round trip to the browser. As a result, the application will consume less server, client, and network resources.<\p>
Download Description
One of the questions that experienced web developers typically ask when learning the ASP.NET framework is this: When I want to transfer control to a new page from the current page, how do I create an instance of the next page and pass it the state of the current request? To accomplish this, the default mechanism provided by the ASP.NET framework is to redirect the browser to the next page using the Page.Navigate() method. This approach to page navigation can be the cause of numerous undocumented dependencies between ASP.NET pages, their possible query string arguments and items stored in the Session. It also does not allow type checking to be done at compile time on the state information passed between the pages. In this article, Andy Elmhorst shows us that it is possible for ASP.NET pages to communicate elegantly with each other as real objects. In the process, the application will save a round trip to the browser. As a result, the application will consume less server, client, and network resources.
|
Create a Custom IHttpHandler to Allow ASP.NET Pages to Communicate with Each Other
List Price: $8.00
Available from Amazon
Price: $8.00
| |
|
|
|
|
