The article uses Session to store ViewState, not Cache. |
| Peter Bromberg replied to Michael Urquiola at 21-Nov-07 05:39 |
| It also talks about reducing or even eliminating ViewState as the first step one should take. Memory on the WebServer is cheap, and extremely fast. I don't understand why Caching would supposedly be "good for single user performance" since it is application-wide and works for all users. But again, the example code (unless you want to go back to the previously mentioned article) does not use Cache at all. If you are using an animal such as a GridView control, which spews out horrid amounts of ViewState into the page, you have not got the choice of "streaming out just the data we need on demand" -- GridView will lose much functionality -- such a Paging / Sorting -- if ViewState is disabled. |
| Biography |
Peter Bromberg is a C# MVP, MCP, and .NET expert who has worked in banking ,financial and telephony for 20 years. Pete focuses exclusively on the .NET Platform, and his samples at GotDotNet.com have been downloaded over 56,000 times. Peter enjoys producing 3D raytraced digital photo collage with Maya, the beach, and fine wines. You can view Peter's UnBlog, IttyUrl, and BlogMetafinder sites.
Please post questions at forums, not via email! |  |
 |
|