Shulou(Shulou.com)06/03 Report--

This article is to share with you about the misunderstandings of Ajax. The editor thinks it is very practical, so share it with you as a reference and follow the editor to have a look.

Like flashing fonts, "splashing" pages that used to be popular, "splashing" pages often have a "skip introduction" or "direct access" button, and use rounded corners, but this time it's more dynamic?

Let's take a look at some misunderstandings about Ajax, clear the fog and discover the truth.

Myth 1: AJAX is the abbreviation of Asynchronous JavaScript and XML. When you write this word, you should spell it in capital letters, or you will appear ignorant.

In fact, according to Jesse James, the creator of the word Ajax, Ajax is more than an acronym. It is a whole of a series of technologies that are combined in a specific way. It includes JavaScript,CSS, DOM and using XMLHttpRequest object to transfer data between client and server. The format of data passed from the server to the client is not necessarily XML, but can also be JSON (objects in Javascript) or other data formats. In short, the transmission of data is small and incremental (instead of traditionally refreshing the entire page). So, if you want to show off that you are a tech expert, use Ajax instead of AJAX. Judge for yourself whether you want to show off or not.

Myth 2: take a look at Gmail and Google Map. Ajax will make your website more useful.

In fact, using Ajax may enhance the usability of your site, but it may also make your site abominable and difficult to use. The newly designed Yahoo TV program list is such a negative example. The negative comment on the new Yahoo TV program list is that the page flipping function of Ajax makes the usability of all TV programs listed on the original page worse, such as not being able to find in one page, although the page flipping function itself is very beautiful. )

Myth 3: Ajax is just a face-saving project-it just looks cool and visual on the surface.

In fact, if there is a correct design and implementation, Ajax network applications should have better scalability and faster response speed than traditional CGI-type web applications with server-side processing (such as ASP.NET or Java Server Pages,JSP). For technical details, see the first part on Ajax and REST written by IBM's Bill Higgins. This is my summary: traditional CGI type, server-side processing as the main body of the network application, the client does not save (network application execution) state (Stateless), state preservation is completely implemented by the server (Stateful server). This makes the results produced by the server (such as data dynamically read from the database) can only be used at one time and cannot be cache down and reuse. This breaks the extensibility principle in the REST architecture. On the other hand, Ajax can save the state on the client side, so that common resources, such as reused data and source programs, can be effectively cached and reused.

Myth 4: Ajax is difficult for ordinary network developers to master.

Ajax is really not easy. But it is becoming less and less difficult to use. There are several factors that make the implementation of Ajax difficult: the support for the compatibility of different browsers, the lack of development tools, and the requirement for developers to change their way of thinking-from web applications dominated by server-side processing to new applications that save state on the client and upload data step by step. However, due to the increasing popularity of Ajax, many development tools and platform providers as well as open source software developers are trying to solve this problem. Here are some useful tools for Ajax developers: Google Web Development Kit (for Java developers), dojo cross-browser platform, script.aculo.us is good at providing visual effects, and (FireFox plug-in) Firebug for debugging JavaScript programs, monitoring XMLHttpRequest, and so on.

Myth 5: Ajax destroys the user's experience of using the browser (Ajax breaks the browser model)

Indeed, the application of Ajax may cause browser problems, such as breaking the "return key" function, leaving users confused and making it impossible for disabled users to use the site at all. But traditional technologies can cause similar problems: for example, the use of frames or Flash often destroys the "return key" function; poor design can confuse users of a site even without Ajax; and it is difficult for disabled users to use the site even with the simplest HTML. These are aspects that require conscious attention and learning, and are not problems that exist only in Ajax applications.

Myth 6: Ajax is a key component of web2.0

It depends on how you define web2.0. I think the difference between web2.0 and web1.0 mainly lies in the social level rather than the technical level. The most important paradigm shift from web1.0 to web2.0 (paradigm shift) is that web2.0 is a two-way network, a read-write network and a social network. Not the "Let's open an online store" network. By this definition, we can implement web2.0 without Ajax at all. Wikipedia can shine on most blogs without Ajax; and Ajax, and social networks don't need Ajax;Flickr to be attractive because it's a social platform for photos, not the DHTML technology it uses.

Thank you for reading! This is the end of this article on "what are the misunderstandings of Ajax". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, you can share it for more people to see!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.