In the previous article "do not learn Ajax, I can do better", I have fully explained the nature of Ajax. In fact, I think
I already have a lot of things, and I need to write something simple.Article? (I cannot understand Ajax"
Actually there will be monographs to illustrate it ).
However, it is sad that many people did not understand this simple thing. Many "experts" have been posted on the BEA Forum before"
I describe Ajax as "Asynchronous Communication" or "Asynchronous connection". Today, I saw the speaker speech at the BEA developer session.
The Chinese version of the draft is still "non-synchronous link". I have to write this article to illustrate how simple it is to connect to the core.
Something wrong.
... (I am sorry to mention that this is omitted here. When I want to write this article, I still ...)
The result of httpxmlrequest is displayed on the page through innerhtml. This process is "Asynchronous browsing" instead
Asynchronous link or asynchronous communication, which is definitely not a different word expression, but many people think that AJAX is asynchronous communication.
Httpxmlrequest communication the XMLHTTP Control establishes a standard HTTP request with the server, based on synchronous Blocking
The TPC/IP protocol is absolutely impossible to be asynchronous. The so-called Asynchronization means that the browser will not block others because it waits for the result to return.
Event. That is to say, even if the result is not returned, other elements can be interpreted and executed, and other events can still respond.
The most intuitive thing is that your mouse can click any element on the page rather than waiting.
"Display the call result on the page" is asynchronous, but the link established in this process is a standard HTTP link,
Is a complete synchronization link!