ASP. NET 2.0 Ajax Day 3: Understanding ASP. NET Ajax Architecture

The architecture of ASP. NET Ajax is based on ASP. NET 2.0 and is an extension of ASP. NET 2.0. This extension is implemented on both the client and server. ASP. NET Ajax is Microsoft's use of a rich client script library and an important server functional layer to enhance ASP. NET functionality. Therefore, understanding ASP. NET Ajax should be learned from the client and server.

(Images are from Google Image Search)
The architecture of ASP. NET Ajax is divided into two parts: client and server.
1) ASP. NET Ajax mainly adds Microsoft Ajax Library to the client extension.CodeLibrary, which contains all client functions and is composed of some JavaScript files that make ASP. NET Ajax work. Microsoft Ajax library has extended JavaScript Functions in an unprecedented manner. For example, you can use the features of various objects to create client scripts, such as class, inheritance, and interfaces; classes that are familiar with C # developers are also extended, such as stringbuilder and timer classes. This greatly simplifies client development.
2) Asp. net Ajax provides a wealth of functions on the server side, including some components and controls, such as ASP. net Ajax extensions and ASP.. Net Ajax Control Toolkit. It makes Ajax development quite simple. This is a deep learning experience in the next day. Of course, this is also Microsoft's consistent style. Common server controls are the ones under ASP. NET Ajax extensions,

Scriptmanager: Manages client scripts. Only one instance is allowed on each page, which is required for each web form that enables ASP. NET Ajax.

Scriptmanageproxy: If the master page contains the scriptmanager control but you want to use ASP. net Ajax function, and each page can only have one scriptmanager instance, so this content page must use a scriptmanagerproxy control to coordinate and scriptmanager script Management

Updatepanel: Any controls in updatepanel can be easily refreshed locally in the Ajax style.

Updateprogress: Displays a status bar (or other animations) to give the user a feedback when making an Ajax request for a long time.

Timer: Used to execute client events at precise intervals. For example, updatepanel is refreshed every X seconds.