<VIEWSTATE Serialization ⁄ >

The most important thing for an end user of a website is the how fast the page loads and our responsibility is to make them happy.

Frequent thing to achieve this is to review the code and write the code such a way that it performs better (in terms of processing time) but what after this ?

What if we still can increase the page serving speed. Apart from the code performance it is the ISP's speed and the size of the page that affects the download speed for a web page.


what if we can decrease the size of the page to some extent ( the size generated after the server side scripting finishes ( i mean the final rendered output)

for every server control if it's ViewState is enabled the data is kept in a viewstate in some encoded format(base64 encoded string as everyone says.)

wo when showing a control on a page keeps data in the rendered output of control as well in the viewstate along with the

state ( previous state) information ( doubles the size of final rendered output..!!)

straighaway coming to the topic we can have this VIEWSTATE buddy help us remotely ( not being rendered with the page so by decreasing the final rendered page out put size)

This can be done keeping the VIEWSTATE in the session or keep it at the server. I am keeping it at the web server as I have got the access to the web server and I have developed one web service that deletes files(holding the VIEWSTATE on the web server) after a day. In short its upto you to write code into the SaveViewState and GetViewState methods.



este é só um excerto do artigo, para aceder ao artigo completo, clique no link em baixo:
this is just a small excerpt from the article, to access the full article please click in the link below:
http://pareshjagatia.blogspot.com/2008/04/viewstate-serialization.html