Design Patterns in the RIA system-why? (Translation)

Preface

 

Many developers use design patterns to solve repetitive problems. With the emergence of new technologies, such as Ria, you will have the opportunity to build applications that are closer to your needs. In this way, some models that describe traditional server-based applications will become more focused on client capabilities. Such a change will evolve gradually. Fortunately, the technologies used today also apply to this new model. This article explores the differences between traditional server-based applications and RIA models, and also describes their common high-level design patterns. Later articles will focus on special design patterns and how to build rich client applications.

Why is it rich?

Ria is an evolution of web development and deployment models. WWW and HTML were originally used to display information and store it randomly. The Web deployment mode is very useful. However, some development teams can't wait to use HTML to create an application interface. In this way, most applications are meaningless in terms of availability due to the collection of user interfaces and the lack of client data control modes.

In early web application development, developers spent a lot of time solving data transmission, resource allocation, business logic, and other basic problems. As a mature and standard technology to solve these problems, it has produced a more attractive web deployment model. Although it is very mature at the end, the presentation layer is still incomplete. The advent of RIA helps developers have the opportunity to implement functional requirements of the user program interface, create more practical applications, reduce the probability of failure, and increase the number of transactions completed.

There are two rich meanings: rich data models and rich user interfaces. Rich data means that the client's user interface can present and cope with more and more complex data modes, so as to process client operations and send and receive data asynchronously. The advantage is that after the page is created on the server and delivered to HTML, the client program provides users with a better experience than interacting with the server. To achieve a highly complex data model, the client allows you to build a highly responsive and interactive application.

Richer interfaces also provide more improved interfaces. HTML can only provide limited functions for user interface control. On the contrary, Ria allows some creative interface control and cleverly matches the data mode. The traditional Internet mode is a linear design method. The only choice for users is to submit pages to the server in batches. The user experience is terrible under such technical restrictions, and such a program is not required by the user. There are many obstacles to continuously processing server requests and page updates, including page response time, poor network bandwidth, and the increasing daily overhead meeting session or State cross-connection requirements. With rich user interfaces, You can migrate from the early mode in which server response affects the operation mode of the entire interface to the mode that only changes the specific area where the request is sent. Essentially, it means that the interface will be divided into individual components to adapt to local changes, server interactions, and communication between internal client components.

The rich result is that you can create a client interface, which is easier to reflect the data and logic of coexistence of richness and complexity.

(Please note! This document shall indicate the translator Rosen Jiang and its source:Http://blog.csdn.net/rosen)