Chapter 11. Optimizing Forms
In a classic ASP.NET website, when you send user input to the server via a form, the existing page in the browser is replaced ("refreshed") by a new page sent by the browser. However, that new page is often almost the same as the existing page. This means, there is scope to cut down the number of bytes sent to the browser to only that content which is new. Also, when the existing page is replaced by the new page, the state of the controls on the existing page is lost, necessitating the introduction of ViewState. This is a problem, especially with GridView controls, which can generate a lot of ViewState overhead.
You can dramatically improve form responsiveness by:
- Reducing the number of trips to the server
- Speeding up ...
Get ASP.NET Site Performance Secrets now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
