Overview of ASP. NET Atlas Framework

I. Introduction

Code map is a new ASP. NET web development technology, in ASP. NET 2.0 Server development platform integrates Client-side Script Libraries. Atlas's AJAX policy for web development allows you to call the Server-side web application from the Client-side Script, atlas can process important parts of Client applications without having to update pages on the Server.

This development strategy allows you to establish a new Web application, and has many advantages that surpass traditional Web development, AJAX applications provide better performance, cross-browser operations, and allow you to build richer user interface features.

ASP. NET's Atlas applied this new policy to Web application construction, and added Client and Server development components to greatly enhance the AJAX development capability of Atlas.

Ii. Atlas Objectives

The main objective of Atlas is to provide a wide range of application building blocks for developers in the following two aspects:

1. Help program developers establish Atlas applications.

2. Integrate Atlas client script features in ASP. NET on the Server to provide a wide range of integrated development platforms.

(1) first goal

The first goal of Atlas is to help you build AJAX applications. Due to the complexity of AJAX itself, Atlas manages the complexity of developing AJAX applications for you, features include:

1. APIs provides consistent and object-oriented features in JavaScript program development.

2. Because of browser compatibility, you do not have to write additional programs and deployment components for multiple browsers, so that your Web applications can be executed across browsers.

3. provides Client-side scripts APIs and components that support Rich UI features, so that you do not need to write a large amount of program code to develop AJAX applications, for example, Atlas provides common Drag and Drop actions and minimizes the program code you need when you fasten these HTML controls.

4. The announcement Syntax of Atlas is similar to that of the control declaration syntax on ASP. NET servo end, so that complicated program writing can be eliminated.

(2) second goal

The second goal of Atlas is to integrate Client Scripting in ASP.. NET servo end program development, different from the previous program development, not only focus on the Client side, but focus on the Server side, Atlas also provides the Client side and Server side tools, in whatever circumstances, Atlas can help you deal with most application development, ASP. NET provides the following servo-end features for Atlas applications:

1. integration between the Web Service and the Atlas application will be very useful, such as the Profiles Service.

2. ASP. NET web server controls will generate the Client scripts required by the Atlas application. Using these controls will make it easier to develop the Atlas application, this reduces the work required to learn about the Atlas Client Script APIs and components.

3. integrated development tools such as Visual Studio will provide an environment, error detection, complete description, management, and productivity enhancement during the development and design period.

Iii. Atlas Architecture

The minimum requirements for Web applications are as long as the Atlas Client Script Library is used to call services or applications on the Web server. But as the best development option and tool, you may want to use the Altas component on the Server. The Atlas architecture is composed of both the Client Script Library and the Altas component on the Server:

(1) Atlas Client components

Shows the architecture of the Atlas client script library:

Figure 3 architecture of components on the Atlas Client

The Atlas Client Script Library is composed of some JavaScript (. js) archives, and provides object-oriented features for program development. This is not the previous Scripting development environment. It provides a new consistency and modular layer, the Atlas Client Script Library includes:

1. browser compatibility layer: provides cross-browser compatibility for Atlas scripts.

2. Atlas core service: contains some JavaScript extensions, such as class, namespace, event processing, inheritance, data type and Object serialization.

3. Atlas Base category Library: Contains string builders, Debuggers, Timers, and Tracing components.

4. Network Layer: handles communication with Web services and applications, and manages asynchronous Remote Call methods.

5. UI Layer: provides some Atlas Client capabilities, including behaviors s, Atlas declaration syntax, UI components, and data binding.

6. atlas control level: provides specific Atlas controls for Client-side development. These controls can have data bound, Scripted, and tie to Atlas behaviors such as drag and drop, this layer includes text boxes such as auto-completion, general type controls, ListView controls with data-bound capabilities, and navigation controls.

(2) Atlas servo component

The Atlas servo component is mainly composed of ASP. NET Web Services and ASP. NET Server controls. The following figure shows the Atlas servo component architecture:

Figure 4 Atlas servo component architecture

It means that all ASP. NET features are fully used by Atlas applications.

Atlas also contains ASP.. NET servo components, including Web Services and server controls, which can be combined with Client Script Libraries. Atlas can gain some benefits from Web Services, including:

1. The Profile service can be persistently stored on the Server.

2. The Membership service can provide verification options.

3. The Role service can provide Role-based verification for the Atlas application.

4. the Personalization service can persistently save user-specific data or webpage-specific data to the Server.

5. The Globalization and Culture-specific services can also be called by Atlas.

ASP. NET also includes ASP. the Atlas Server Control of the NET Server Control, but the Atlas server control can send Client scripts. The Atlas Server Control simplifies the process of generating the Atlas Client Script, it is suitable for program developers who want to focus on Servo development. Atlas includes complete server controls such as Button, Label, Option, TextBox, CheckBox, HyperLink, Validator, and other existing ASP. NET server controls are very close, and some Atlas controls can issue JavaScript to generate Client behavior, including the HoverBehavior control, ClickBehavior control, Popup control, and AutoCompleteBehavior control, all controls will be integrated into Visual Studio, so you can use them in design mode as you are using Generally, ASP. NET Server controls are common.

The Atlas Framework installation package has also been available for beta download and use. Five Hands-On-Lab are provided. To understand the mysteries of the Atlas Framework, I have actually installed and tested it, when we finish the first three labs, we still cannot clearly feel the obvious difference between them and manual or other AJAX libraries. Is it Microsoft's exaggeration? However, after finishing the fourth Lab, the feeling of Atlas came, and we could obviously experience the advantages of Atlas. It really had the taste of the Framework level, not just the level of a Library, in the TextBox Control of the Web, you need to start a few English texts with a Key like an electronic dictionary. Then, the screen displays the relevant English text for selection, or a friend once asked me, he wants. NET 1.0 TextBox Control, enter several order numbers starting with, and then the screen is... I told him directly that the records related to database tuning are listed on the screen for selection by business personnel ~ I won't. Two years later, the answer is here ~ Atlas Framework, simple to incredible, the core part is only two lines of program code... it is enough to defeat the skill that I have not been able to practice before (OH ~ I'm still young and far away from a child !).

After reading the functions and architecture of the Atlas Framework, are you eager to get started! I understand modern people's quick start, and I don't have the power to be patient. I will study AJAX theory for more than a year and a half, so I will introduce the hands-on Labs of Atlas Framework in the next phase, we will teach you how to directly wave the powerful sword of Atlas, and you will learn what Atlas is. With Sense, we will discuss more in-depth AJAX theories. You will feel better.

Figure 5 Automatic completion of Atlas servo