Ajax Basics Tutorial (1)-ajax Introduction 1.7 Design Considerations

Now that you know where to use Ajax, let's talk about some of the design considerations for applying Ajax. Many principles are not different from the principles of Web application, but it is necessary to emphasize. Try to reduce the amount of traffic between the client and the server. If applied properly, Ajax can make your application respond faster, but you will not be satisfied if you pass the excess data back and forth every time a user moves from one domain to another. If in doubt, act according to the standard agreement. If most applications do that, maybe you should do the same. If you have questions, look at the standards for Web desktop applications. A number of patterns have been established for this purpose, and there will be more patterns (www.ajaxpatterns.org) in the future.

When you first use AJAX, your users may not be aware of how the application works. For years we've been telling users that the Web works in some (synchronized) way, while Ajax adds asynchronous components that may run counter to it. Simply put, don't let the user feel strange. When the user leaves the last domain with the jump bar, if the previous application (not using AJAX application) did not save the form, then use AJAX after the application do not save the form.

The most important problem when implementing Ajax is to strive for simplicity, completely from the user, to try to "fool". To take the user to heart, do not do "resume-driven design." If you're just trying to get your new boss to accept you, and therefore use Ajax in your application, this is not appropriate; If you use Ajax to give your users a richer experience, then use Ajax without hesitation. But don't forget that what you will do does not mean that you should do it. Be sensible and consider your users first.

We'll talk more about security later, but let's be clear here that Ajax has some security concerns. Remember, you can view the source code in the browser, which means anyone can know how you create widgets. You must include a Uniform Resource Locator (Uniform Resource Locators,url) When you create a XHR object, so there may be malicious users who can modify your site and run their own code. Careful use of Ajax can reduce this risk.

Back to "Ajax Basics Tutorial-Directory"