ajax|web| procedure One, introduction
An ideal user interface is best not visible to users-only when users need them, otherwise they do not interfere in their work and let them focus on the work at hand. However, this is not an easy thing. Today, we become accustomed to doing our daily work through the less satisfying UI until someone shows us a better way. Now we are beginning to realize how hard our current approach is to do these things.
Because the basic web browser technology used to display the content of the document has been pushed further beyond what it used to be, today's Internet is experiencing this realization.
Ajax (asynchronous Javascript+xml) is a very new name, created for Jesse James Garrett of Adaptive Path. Some parts of Ajax have previously been described as Dynamic HTML and remote scripting.
The advent of Ajax is not just a question of a new name. From a technical and commercial point of view, there is a lot of exciting stuff around Ajax. Technically, Ajax has achieved a great deal of untapped potential in Web browser technology. Commercially, Google and other major businesses are increasingly using AJAX technologies to make the public aware of what a Web application can do.
The typical Web applications we used to use today are under great pressure because the increasingly complex web-based services are maturing and starting to apply to the Internet. New technologies scramble to overcome these problems, and Ajax can better express these ideas using only existing Internet technologies.
With Ajax, we've reused a bunch of old technology but expanded the range of what they were able to do. We need to be able to manage this complexity that we introduce. This article discusses how to implement these technologies, and also discusses the issues of managing large AJAX projects. We'll introduce Ajax design patterns and how they can help us get the job done. Design Patterns help us capture our knowledge and experience, communicate with our current technology and make it available to other objects. By introducing the rules to the code base, they make it easy to create applications that can be modified and extended to work according to changes. Using design patterns for development is even a joy!
Why is Ajax a rich client?
Building a rich client interface is more complicated than designing a Web page. So is something that led us to do this? What are the benefits? What is the rich client?
A rich client has two key features: It is rich, and it is a client.
Let me give you a little explanation. Richness refers to the way the client is. A rich client model-refers to its ability to support various input methods and to respond intuitively and in a timely manner. Although we call it "rich," it must be as good as a modern desktop application like a word processor and a worksheet. Let's look at the implementation techniques that are specific to this goal.
Second, compare user experience
Here, let's discuss an instance of a worksheet program. When I enter some simple formulas on a worksheet, I can interact with it in several ways-edit the data in the field, navigate the data with the keyboard and mouse, and rearrange the data by dragging the mouse.
When I'm manipulating these, the software gives me feedback-the mouse cursor changes, the button highlights when I move the button, the selected text changes color, the highlighted window and dialog box are displayed in different forms, and so on (Figure 1).
Figure 1 This desktop worksheet application illustrates the possibilities for multiple user interactions . |
These are the main features of today's user-rich interactions. Is such a worksheet application a rich client? Not yet.
In a worksheet or similar desktop application, both the logical and data models run in a closed environment-where they are visible to each other, but shut out of the world (Figure 2). My client definition is a program-it can communicate with a different independent process-typically it runs on a server. Traditionally, the server is larger and stronger than the client and stores massive amounts of information. The client allows end users to view and modify this information, and if some customers are connected to the same server, it allows them to share the data. Figure 3 shows a simple diagram of a client/server architecture .
- Ajax: A new way to build Web apps
- Discussion on the error handling mechanism of AJAX (2)
- Discussion on the error handling mechanism of AJAX (1)
- First experience. NET Ajax Brushless New technology
- A brief analysis of Ajax development Technology in Rails system (4)
