IIS6 http compression with ASP.NET: is there any disadvantage especially when using ajax updatepanel ?
IIS6 http compression with ASP.NET: is there any disadvantage especially when using ajax updatepanel
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
IIS6 http compression with ASP.NET: is there any disadvantage especially when using ajax updatepanel ?
I dont think so.I have worked with UpdatePanel for quiet a long time and always IIS Http compression was enabled.Once the page is sent to server during postback then complete page life cycle takes place as if its a normal webpage.During the prerender phase only the markup of content which is inside the ContentTemplate tag of Updatepanel is rendered and sent back to browser.Here in browser that markup is used to update the UI.
Also if you use tools like YSlow and PageSpeed to analyze the performance of webpage then thse tools take Http Comprssion as one of the deciding factor.Enabling compression is one of the prerequistis.
You can check for the extensions which are marked for compression by checking the metabase.xml file in the following location :- Sysroot\Windows\System32\inetsrv\metabase.xml . Rem not to modify the content of this file.