Overview of the overall architecture of Atlas

The following figure shows the overall architecture of Atlas shown in the demo of shanku niyogi and Nikhil Kothari on PDC 2005.

(Stolen from Nikhil Kothari ppt)

According to Nikhil Kothari, Atlas is not designed to become a common Ajax class library, instead, it becomes an end-to-end application framework that develops and integrates the interaction between the client and the server. It allows developers, you can use both XML declaration and Script Programming to quickly integrate components and make the Script Function and ASP. the integration of Net Applications is neat and tidy, and it is not abrupt.

Atlas provides a client framework and services, mainly including
1. The browser compatibility layer encapsulates differences between browsers to facilitate the independence of browsers at other levels of functions. Currently, Internet Explorer, Safari, and Firefox are supported.

2. The script kernel includes a complete JavaScript class system that allows you to use the construction in standard Oop, such as namespace, class, interface, inheritance, enumeration, and proxy (delegate. The purpose is to provide a mechanism to encapsulate data, logic, and behavior into classes so that developers can develop scripts like other programming languages.

3. Base Class Library, subject. inspired by the net framework, it provides convenient basic types such as stringbuilder, debug, event, and idisposable, and provides a client networking Layer Based on XMLHTTP through the webrequest and webresponse classes, you can use methodrequest to interact with server services such as aspx and asmx. Serialization, especially the JSON serializer, is also provided. This class library also provides profile and authentication services that can be integrated with the corresponding services on the server.

4. The component model and UI framework introduce the concept of components that can self-Describe the object model. These models can participate in the lifecycle mechanism of a top-layer application class management, it can be established through declaration or programming, and data and interaction can be transmitted through binding and events. The UI framework provides controls related to dhtml ui elements and how to attach actions to these controls, such as drag/drop and verification of input control data.

5. Controls and components, provides components such as timer and counter, and controls such as listview and map controls

Atlas also provides server-side infrastructure,
1. The server control framework defines a new control scriptmanager to manage the scripts sent back to the client and the XML-script identifiers generated by the server control. Server controls can also participate in request processing by implementing iscriptcomponent, and also provide server-side objects that correspond to the client component model type.

2. The network service bridge allows client scripts to access common network services (asmx) and indigo-style services (SVC), or directly access the webmethod declared on the webpage, this is a statement similar to the following:

<SCRIPT src = "myservice. asmx/JS"/>

The service automatically generates the javacript proxy class. It also provides infrastructure for JSON protocol calls to server services.

3. The application service bridge provides several ASP. NET application services through the network service bridge. For example, you can perform user authentication through the member service and access/update user data through the profile service.

For more information, see Nikhil Kothari's blog and the following two slides.

Atlas Architecture Overview

Prs312 ASP. NET: Future Directions ctions for developing rich Web applications with Atlas (Part 1)

Prs420 ASP. NET: Future Directions ctions for developing rich Web applications with Atlas (Part 2)