Question { DSRC, 33644 }
Where is ViewState information stored?
Answer
Storage Options
Because it implements the Provider Pattern, you have at your
disposal two ways of storing ViewState (with more to come):
* Save To Cache: save ViewState in Cache, on the server
* Save To XML: saves ViewState into an XML file on the
server
The storage option you choose, depends on your requirements
as well as the constraints of your hosting environment.
Save To Cache: it is recommended for those situations where
you have a moderate volume of visitors. Pages will be served
faster (since we are accessing memory to retrieve
information). Since Chache is recycled automatically by the
server when memory is needed, it is important to know what
your hosting provider memory limits are, and what volume of
users you expect at any given time.
The Cache solution, allows you to specify the number of idle
minutes that you want the viewstate to be kept in memory
before being recycled (cacheMinutes attribute).
In case of premature recycling, the page will not fail, but
be redirected to itself, thus instantiating a new caching cycle.
Save To XML: it is recommended for high volume sites. Pages
will be served fast, and viewstate stored and retrieved from
xml files saved in a directory of your choice (virtualPath
attribute) that will require r/w permission.
There will be one file per user, and files will be deleted
at a configurable interval (fileCacheMinutes attribute).
Since there could be multiple ViewState in any given file
(if for example a user opens a pop-up), you can also specify
the number of minutes that any given ViewState entry can be
idle before being deleted (recordCacheMinutes attribute). If
you have a lot of pop-ups in your site, recordCacheMinutes
should be set to few minutes.
In case of premature recycling, the page will not fail, but
be redirected to itself, thus instantiating a new caching
cycle.