Sound
This chapter is translated by netizen azure, and the author is responsible for the post-toll of articles.
-------------------------------------------------- ------------------
RIA design
Now the enterprise application is typically a layered design and is also based on this organizational program logic. Below is a typical N layer application model:
Figure 1: Typical N-layer application
There are three main layers: Client Tier, Middle Tier, and Enterprise Information System (ENTERPRISE INFORMATION SYSTEM ": EIS) layer. Each of the main layers is divided into several layers depending on the logic.
The client layer contains the user interface and the program interface containing the logic of the presentation content, processing the user session, the status management service layer contains the system's service logic integrated layer contains the connector and adapter resource layer containing the remote program and the data source contains the database. Information and enterprise information resources like ERP and XML files
The structure of a typical network deployment system in J2EE is as shown in the figure:
Figure 2: Typical web deployment system
In the network deployment system, the logic that determines the program process, content creation and content delivery is existing in the intermediate layer, because the main feature of the traditional web application is a client browser request / response model. If you want to pass the interface, the system needs to format and compile content in HTML in HTML before it passes through the intermediate layer. For any modification of any representation, it is necessary to issue a request to the server, and the response is a portion of the entire page rather than just make changes. In the traditional network model, Applet, JavaScript / DHTML and other methods are used instead of the customer layer solution, which has never become mainstream, mainly because of a variety of technical issues, mainly compatible with different browsers. The rich customer model can better reflect the structure of the program, as shown below:
Figure 3: Typical Fujian model
Unlike J2EE programs, the client's request can cause the system to generate a page and return to the client, a RIA can support smaller units or components, from small to a voting problem to a complete view or interface, rich customer model The interface is broken down into a small unit module that can communicate with both the user directly interact with the server.
This transition that transfers the application's design from a relatively independent page to component-centered transitions will enhance the customer layer to a new level and make the client layer more flexible. The rich client is no longer the final end of the server response, which also enables the performance of the program, and the feeling of the user is as if the program does not need to communicate with the server or only occasionally needs to communicate.
The last RIA model is characterized by event models. Like traditional models, the server receives the request from the top to the top to create a client interface, you do not need to predict the order of the event. Since each component is independent, there is no need to make a response to the entire view because of a request. To make each component have the ability to transmit information to the server requires each group to know how to handle the server to pass the server. In RIA, the client and server-side interaction data are not synchronized so that you can control component creation information to send to the server and process the response to the server, which can be a more zero-scattered control de-coupling and separating the program function and form a service-oriented service. Program structure. (Please pay attention! Quote, transfer this article to note: rosen Jiang and the source: http://blog.9cbs.net/ROSEN
