-
Open-ViewState is an HTTP-Module that requires no changes nor recompilation
of any application source code.
-
You Just need to add the Open-VieState .dll to the /bin directory of your
application and configure it's functionality through entries in the web.config
file.
-
When a response contains ViewState information, this is removed and placed
in the server-side storage medium selected at setup (see setup information
section). Instead of the entire blog of ViewState, the client's browser is
served with a hidden Key, that will allow retrieval of the stored viewstate
information on its next request. This way, it reduces ViewState to virtually nothing.
-
On the next request, the ViewState information previously stored is
retrieved to be made available for use and modification by the application as
usual. Just before the resulting HTML is sent back to the client in the
response, it is once again stored on the server.
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.
see setup example
Setup is very simple and may only require a minute.
-
Copy the ViewState-Server .dll in your application's /bin directory
-
Give r/w access to the ASPNET (win2k) or Network Services (win2003) to the folder where XML files will be stored
-
Make a few entries in your web.config as shown in the example link
see license agreement
Licenses are per Domain. Simply put, you buy ViewState-Server, and you can use it on any page that is invoked with the same base url.
Please see the full License Agreement in the link above.
see live demo
View the source of the page in the demo link, and look for the __VIEWSTATE tag.
You will see that its value is simply a guid key. All ViewState information is saved on the server.
buy ViewState-Server for .NET 1.1
Price: 20.01€ (EUR)
buy ViewState-Server for .NET 2.0
Price: 20.01€ (EUR)
Upon confirmation of your payment (it's usually immediate), you will be able to download
and use ViewState-Server according to the license agreement above.
We use PayPal for transaction processing. You do not need to have a PayPal account
in order to purchase this product. PayPal allows you to use your Credit Card like any other
credit card processing provider.