How to trace that Viewstate compression through RadHiddenFieldPageStateCompression is used

[CSurieux]

Hello,

Refrering to my unanswered thread
http://www.telerik.com/community/forums/aspnet-ajax/compression/radhiddenfieldpagestatecompression-gzip.aspx

and now porting to .net 4.

Being unsure that I am obtaining compressed Viewstate (they are so big), I want to trace on server the fact that the that it is compressed, Fiddler or FireBug can't be used easilly on a production site.


Is there a way to activate some server side trace in Telerik tools or to trace thta Viewstate is going through my .browser file and the control adapter is effectivelly usefd.

Thanks
CS

[Simon]

Hello Christian Surieux,

Since the .browser configuration setting is there, then ViewState must be compressed as expected, unless there is a bug, in which we doubt as this functionality has been tested and available for a long time and we have not received any reports during this time.

I suggest you compare both ViewStates - one time when compression is enabled and one when it is not - and in this way see whether there is any difference.

Additionally, the headers of each response indicate whether the *whole* content is compressed or not and not just a part of it. So one cannot tell whether ViewState is compressed only by judging by the headers.

I hope this helps. If you have additional questions, please let me know.

Kind regards,
Simon
the Telerik team

[CSurieux]

Hi Simon,

Sorry to say that there are plenty of forum threads related to Viewstate compression not working and many of them without any response.


I have compared with Fiddler and no compression is done respecting all the configuration recommended in Blogs and threads.
My problem is that I am unable to see if my ADNBrowserFl.Browser is used or not !
My application being too large, I am using trace listener and traceswitchs to debug it and I would appreciate to know how to trace telerik tools for viewstate compression server side!!!!

Today my application, using many Telerik controls, generates extremely huge Viewstates (see www.addonnice.com and its internal pages).

Until these days I had no necessity to fight on this point but as my web site visits increase it raises on the top of the problems to solve list.

And now I am migrating the Web Application to framework 4 and I am sorry to say that I can't find a way to combine the new features for Viewstate with Telerik controls and Telerik Viewstate compression tools.

I am very disappointed for this lack of factual documentation.
Seems that the help file is outdated and that the blogs do not present an overall view on how to deal with this for an App wich is 100% based on Telerik for its GUI.

Best regards.
CS

[Simon]

Hi Christian Surieux,

The easiest and surest way of detecting whether ViewState is compressed when using RadHiddenFieldPageStateCompression is to observe the __VIEWSTATE hidden field in the page source.

<input type="hidden" name="__VIEWSTATE" id="__VIEWSTATE" value="..." />

This field's value always reflects the size of the ViewState. In pages where ViewState is huge, the difference in the size when our page state compression is on and off is directly visible. You can test this now by observing the size of the field when our control adapter is confgured and when it is not.

Kind regards,
Simon
the Telerik team

[CSurieux]

Hi Simon,

Sure I know....but this is not the answer I am expecting because it doesn't solve the problem....

Regards
CS

[Simon]

Hello Christian Surieux,

Perhaps I am missing something. I thought you only wanted to detect whether our ViewState compression worked or not.

Can you please let me know what is the problem that you want to solve?

Regards,
Simon
the Telerik team