All told, over 9kb of data is sent, when in fact only five bytes of data were needed to make this particular request. The response portion of the Update Panel's update request is shown in the Firebug console display on the left; it is a specially-formulated pipe-delimited string that is broken up by the client script and then reassembled on the page. NET AJAX sets the property of the HTML element on the client that represents your Update Panel.
The Script Manager control provides extensive support for localization of script strings and user interface components; however, that topic is outside of the scope of this whitepaper.
This means that the Update Panel can work with the default data-bound controls (such as the Grid View), with user controls, and they can be programmed in script.
By default, when a partial page render is triggered, all Update Panel controls on the page will be refreshed, whether or not the Update Panel controls defined triggers for such action.
To understand how the Update Panel works, so that you can best decide when its use is appropriate, you should examine the AJAX exchange.
The following example uses an existing site and, Mozilla Firefox with the Firebug extension (Firebug captures XMLHttp Request data).
However, its server-side processing model has several drawbacks inherent in the technology: Enter Microsoft's ASP. AJAX, which stands for A synchronous J ava Script A nd X ML, is an integrated framework for providing incremental page updates via cross-platform Java Script, composed of server-side code comprising the Microsoft AJAX Framework, and a script component called the Microsoft AJAX Script Library. NET AJAX extensions also provide cross-platform support for accessing ASP. This whitepaper examines the partial page updates functionality of the ASP.