Problems with the use of AJAX

Problems with the use of AJAX

The usage of AJAX is growing rapidly, which is why it contains many problems. We hope that over time these issues will be resolved and that AJAX will become the ideal choice for Web applications.

In this section, we list some of the issues that AJAX is currently experiencing.

(1) Complexity has increased

• Server-side developers need to understand html client pages and the display logic that will be required in server-side logic.
• Page developers must have JavaScript skills.

(2) AJAX-based applications may be difficult to debug, test, and maintain

• JavaScript is hard to test - automated testing is hard.
• The modularity in JavaScript is weak.
• There is no design pattern or best practice guide.

(3) The toolkit/framework is not yet mature

• Most of them are in the testing phase.

(4) XMLHttpRequest has not been standardized

• Future versions of IE will address this issue.

(5) XMLHttpRequest is not supported in the old browser

• iframe will help.

(6) JavaScript technology dependency and incompatibility

• Applications must be enabled to run.
• There are still some browser incompatibilities.

(7) JavaScript code is visible to hackers

• Poorly designed JavaScript code can raise security concerns.

AJAX security

On the server side

• AJAX-based Web applications use the same server-side security scenarios as regular Web applications.
• You can .xml authentication, authorization, and data protection requirements in a web file or program.
• AJAX-based Web applications are subject to the same security threats as regular Web applications.

Client

• JavaScript code is visible to users/hackers. Hackers can use JavaScript code to infer server-side weaknesses.
• JavaScript code is downloaded from the server and executed on the client ("eval") and can be compromised by malicious code.
• The downloaded JavaScript code is constrained by the sandbox security model and can relax the signature JavaScript.