Hi,
I am using the Radcompression module version 2011.2.915 and have enablePostbackCompression set to true along with RadHiddenFieldPageStateCompression in the App_Browsers folder.
The page in question has a RadGrid sitting within a RadAjaxPanel. The Grids datasource is being persisted in viewstate, hence it can get quite large.
I have noticed using Fiddler however that only the first callback appears to have its viewstate compressed.
The bytes sent for the pageload, followed by its subsequent callbacks are as follows with the hiddenfieldpagestatecompression on
891 21,920 250,414 232,786
the above is all in bytes
when disabled however and following the same steps I get as follows
987 118,592 250,424 233,082
I would expect the first number (the page request) to be just about the same as there is no viewstate.
As expected the first call back is significantly larger due to the lack of viewstate compression.
I was however surprised to see that the subsequent callbacks bytes sent were almost the same. This suggests to me that the viewstate compression has stopped taking place. The page still works fine however so it has not been corrupted which is good.
I was wondering if anyone else has encountered similar issues or not?
Thanks
Matt
I am using the Radcompression module version 2011.2.915 and have enablePostbackCompression set to true along with RadHiddenFieldPageStateCompression in the App_Browsers folder.
The page in question has a RadGrid sitting within a RadAjaxPanel. The Grids datasource is being persisted in viewstate, hence it can get quite large.
I have noticed using Fiddler however that only the first callback appears to have its viewstate compressed.
The bytes sent for the pageload, followed by its subsequent callbacks are as follows with the hiddenfieldpagestatecompression on
891 21,920 250,414 232,786
the above is all in bytes
when disabled however and following the same steps I get as follows
987 118,592 250,424 233,082
I would expect the first number (the page request) to be just about the same as there is no viewstate.
As expected the first call back is significantly larger due to the lack of viewstate compression.
I was however surprised to see that the subsequent callbacks bytes sent were almost the same. This suggests to me that the viewstate compression has stopped taking place. The page still works fine however so it has not been corrupted which is good.
I was wondering if anyone else has encountered similar issues or not?
Thanks
Matt