Last Friday, according to Harry Fuecks, a spokesman for the PHP 2006 UK Conference, many coding AJAX applications tend to forget network latency, resulting in poor user experience.
Fuecks has been engaged in software development since the early 1990s S. He warned that developers only work on a local machine and will not experience latency issues like real Internet users.
Fuecks is the founder of the JPSpan program, which allows PHP developers to include AJAX functions in their web pages. He said at the meeting that, because Internet service providers cannot control the length of latency experienced by users, developers should not determine that end users will get the same service speed as they did when writing code. Fuecks pointed out that many well-known AJAX success stories occur in organizations with large amounts of resources such as Google. "These problems are almost impossible if you invest a lot of money," he said ."
When submitting multiple requests to the server, another problem that may occur in the AJAX application is that the response may be returned in the wrong order. This will cause unstable applications and availability problems, Fuecks warned.
He also pointed out that many developers have not considered this issue in the tool groups currently applied. "No public AJAX framework helps solve this problem ."
Fuecks recommendation coders use an AJAX agent in their development environment to simulate the latency issue after an application is configured in the production environment.
Fuecks further criticized the common AJAX method, which he called "beautiful slogans ". Problems caused by the execution of browser JavaScript, such as memory leakage, indicate that they are not suitable for the running time of strict, long-term running application software.
Fuecks also uses AJAX improperly, and uses it to submit forms even if there is an appropriate mechanism. He also pointed out that AJAX cannot quickly replace local applications. "Remember, in a browser, you cannot access the file system ."
(