We are currently using version 2009.3.1314.35 and do not see the Compression control in the Toolbox.
What do I need to do to get this control in the toolbox? Do we need to upgrade to another version or is it something I can include from our present version?
I've noticed that on the following link (http://blogs.telerik.com/blogs/posts/09-02-27/optimization_tip_radcompression_for_viewstate.aspx), it says all you need is version ASP.NET AJAX Q3 2008 SP2 or later. As noted above, we are using version 2009.3.1314.35 and do not see the Compression control in the Toolbox.
How can we enable this feature?
What do I need to do to get this control in the toolbox? Do we need to upgrade to another version or is it something I can include from our present version?
I've noticed that on the following link (http://blogs.telerik.com/blogs/posts/09-02-27/optimization_tip_radcompression_for_viewstate.aspx), it says all you need is version ASP.NET AJAX Q3 2008 SP2 or later. As noted above, we are using version 2009.3.1314.35 and do not see the Compression control in the Toolbox.
How can we enable this feature?
3 Answers, 1 is accepted
0
BaiH
Top achievements
Rank 1
Rank 1
answered on 12 Jul 2010, 03:43 PM
William,
RadCompression is not a control. It is a HTTPModule and PageAdapters, so they should not be in the toolbox.
As to how to enable it, maybe you should check the article you have pasted. In the very beginning there is a HOW DO I ENABLE VIEWSTATE COMPRESSION? section.
--BH
RadCompression is not a control. It is a HTTPModule and PageAdapters, so they should not be in the toolbox.
As to how to enable it, maybe you should check the article you have pasted. In the very beginning there is a HOW DO I ENABLE VIEWSTATE COMPRESSION? section.
--BH
0
Bill
Top achievements
Rank 2
Rank 2
answered on 12 Jul 2010, 06:08 PM
BH, I updated the web.config file and added a browser file with the attached code, but doesn't seem to be working. I am using IIS7 & Windows 7.
The reason why it doesn't seem to be working is the test I've done with Fiddler (v2.2.9.7).
With the attached code not included in the project, I simply browsed to a specific page and got 111,333 bytes xferred on the page. If I used the GZIP Encoding option to see how many bytes should have gotten xferred if the compression was on, it was 17,592 ( a savings of about 80% or so).
I then included the attached code in the project and executed going to the same exact page. It was still 111,333 bytes indicating that the compression didn't work. It should have reduced it to the 17,592 bytes.
I also added the extra lines in the web.config file (see attached file), but still doesn't work. I'm getting the same number of bytes xferred with and without all the code.
What do I need to do in order to get the compression working for the project?
fyi, I got it to work after including another parameter in the web.config file. Situation resolved.
thanks,
bill
The reason why it doesn't seem to be working is the test I've done with Fiddler (v2.2.9.7).
With the attached code not included in the project, I simply browsed to a specific page and got 111,333 bytes xferred on the page. If I used the GZIP Encoding option to see how many bytes should have gotten xferred if the compression was on, it was 17,592 ( a savings of about 80% or so).
I then included the attached code in the project and executed going to the same exact page. It was still 111,333 bytes indicating that the compression didn't work. It should have reduced it to the 17,592 bytes.
I also added the extra lines in the web.config file (see attached file), but still doesn't work. I'm getting the same number of bytes xferred with and without all the code.
What do I need to do in order to get the compression working for the project?
fyi, I got it to work after including another parameter in the web.config file. Situation resolved.
thanks,
bill
0
Accepted
Hello Bill,
As you may have noticed from the mentioned article, RadCompression's http module kicks in only on ajax post requests by default. Therefore there will be no difference in the response size on initial page load as long as the http compression is concerned.
Kind regards,
Rosen
the Telerik team
As you may have noticed from the mentioned article, RadCompression's http module kicks in only on ajax post requests by default. Therefore there will be no difference in the response size on initial page load as long as the http compression is concerned.
Kind regards,
Rosen
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items