Optimizing And Compressing ViewState has never been so easy!

Introduction

Flesk.NET Viewstate Optimizer is a unique technology that overrides sending ViewState object to your client's browser! This means that your client's browser will no longer receive those large hidden field values, which thus reducing downloading time. Instead, Flesk.ViewStateOptimizer saves the page's Viewstate hidden field to a file, on the server side, speeding up processing time, downloading time and data.

Combining Flesk.NET Viewstate Optimizer and Flesk.NET Accelerator, you can benefit from reducing downloading data and downloading time up to 30 times faster! No other components do the same or give the same results!

Flesk.NET Accelerator and Viewstate Optimizer are now released with versions targeted for the .NET Framework v2.0

How does it work?

Flesk.NET ViewStateOptimizer has several Viewstate optimization possibilities that can be set through the web.config file. From viewstate data compression to saving viewstate on server farms, anything can be possible. This means that Viewstate Optimizer can persist values using server side Sessions or files saved on shared locaton accessible by a server farm, or by using common viewstate hidden field value on client side, with the ability to compress data.

Viewstate Optimizer can use different storage methods:

  • save to file (saves ViewState into a file, server side)
  • Session (saves ViewState into a Session variable, server side)
  • Default (default ViewState saving method, sends hidden fields to client side)

Other parameters are:

  • depending on the storage method setting, Viewstate Optimizer can be set to compress viewstate value, so that it can be significantly smaller than the original value
  • the request behaviour of viewstate can be set to be generated on the first request to a page and then reused in the following postbacks, or to be generated on each request to a page.
    A common scenario where viewstate set to be generated on each request can be usefull is in Content Management frameworks: page loads up some controls on postback based on some state stored in hidden input values, handles events and as a result of those actions purges the control collection and loads new controls. Standard Viewstate Optimizer configuration persists the Viewstate using the same GUID as the original page.
    If the user then hit's refresh (F5) in the browser, the data is posted again, the framework loads up it's controls based on the original state but the viewstate value now matches the new controls. This also happens with any change to the viewstate between postbacks, when users back up or use refresh in their browsers.
    The solution was to make Viewstate Optimizer generate GUID's each and every time the viewstate is persisted. Only then is the viewstate truly unique for each page.

Features

  • Reduces downloading time of your website or web application, by not sending back the page's Viewstate hidden field.
  • This component is setup individually. It is not shared by all the webserver's websites, but only by your website or webapplication. This means that you can install it in your hosting account without changing any webserver's configuration.
  • Runs on .NET Framework v1.1 and v2.0. No configuration required. Only a few lines on your web.config file is all you need to change.
  • Greatly reduces bandwidth traffic from your webserver, reduces Posted data from your client's browser, and speeds up your web application!
    Supported by WebFarms
  • Compresses the ViewState value. This means that ViewState is sent and returned to/from client's browser or saved into local file, on server, compressed, thus reducing ViewState's value length and increasing speed even more!
  • This release of the Viewstate Optimizer is designed to meet the requirements of
    customers that are unable to change the base class of their pages.
  • The Flesk.Accelerator.Page class now provides two static methods that allow calling the viewstate procedures from within any page class.
  • ViewState files can now be persisted on shared location accessible by all servers in a server farm.