14. August 2007 18:46
So I am writing an application with ASP.NET AJAX and using the update panel to update certain controls. So there I was creating the page without any AJAX and with normal postbacks and when I was finished I just added a script manager and an update panel and voila everything works wonderfully. So I told myself: "This is so easy to implement that there must be some side effects." Usually when something is very easy to implement and so generic efficiency is hurt. So I did a search on updatepanel efficiency and I came across 2 articles: Jeff Prosise's Update Panel Tips and Tricks and Nick Riggs' Update Panel's Update Mode Property Efficiency. I must say I was not surprise with Jeff's statements on using update panels and the efficiency hits, but I was surprised with Nick's findings on using the different update modes. So being the skeptical person I am I go to the source when it comes to AJAX, the good all mighty of AJAX, the know-it-all of AJAX, the one and only one DevTheo: Mr Jay Kimble. Indeed he did confirm Nick's findings. The reason? When using the update panel and an update is fired the whole page life cycle is re executed (just like a post back) and for that you need the viewstate, which usually composes most of the page's weight.