Forehead
Many developers use design patterns to resolve repetitive issues. With the emergence of new technologies, such as RIA, you will have the opportunity to build applications that are closer to user needs. In this way, some of the modes describing the traditional server-based application will become more focused on the client's ability. Such a change will be gradually evolved, fortunately, the techniques used today also apply this new model. This article explores the difference between the traditional server-based application and the RIA mode, and also expounds the high-order design patterns they share. The later article focuses on special design patterns, and how to build a client application. Why is it rich?
RIA is a evolution of web development and deployment mode. WWW and HTML were originally used to display information and randomly stored for this information. 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 status due to the boundaries of user interface control, and lack of client data control mode. In the early Web application development, developers spend a lot of time to solve the data transfer, resource allocation, business logic, and other basic issues. As a mature and standard technique to solve these problems, there is a more attractive web deployment mode. Although it is already mature, the expression layer is still imperfect. RIA's arrival helps developers have the opportunity to implement the functional needs of the user program interface, create a more practical application, reduce the failure, increase the number of transactions. Rich meaning has two, rich data models and rich user interfaces. Rich data means that the client's user interface can express and address more more complex data modes, so that the client's operation and asynchronous send, accept data. The advantage is that the client's program provides users with better feelings than the server's interaction than the server is created and delivered to HTML. In order to achieve highly complex data modes, the client allows you to build a high response, interactive application. Rich also means more improved interfaces. HTML can only provide limited functions for users' interface control, and the RIA allows some creative interface controls, smart and data patterns. Traditional Internet mode is a linear design, and the only option of the user is to submit a page to the server with a batch method. Under this technical limit, the user experience is very bad, which is not required by the user. Continuous processing server requests and page updates There are many obstacles, including page response time, poor network bandwidth, and daily overhead that meets session or State cross-connectivity. With a rich user interface, you can drive from early, server responding to operational mode of the entire interface, migrating to modifying only a specific area of the issued request. Essentially, it means that the interface will be decomposed into communication with individual individuals, and to accommodate local changes, server interactions, and communication in internal components. The rich result is that you can create a client interface, which is more easily reflected in the data and logic coexisting with complexity.
(Please pay attention! Quote, transfer this article to note: rosen Jiang and the source: http://blog.9cbs.net/ROSEN
