Problems With AJAX
AJAX (Asynchronous JavaScript and XML) is the hot and happening new web technology.
When AJAX was introduced last year, it became popular quickly bcoz of its powerful functionality of executing server side scripting and dynamically replacing document contents without actually reloading the current document.
But now developers are busy in finding solutions to AJAX functionality as there are some problems with AJAX and AJAX accessibility.
Even if a user is expecting information to update, they might not notice the actual change in data. In addition, since pages are updated incrementally, AJAX applications may not have distinct uniform resource identifiers (URIs) that can be bookmarked. This can also lead to issues with the Back button not functioning as expected.
JavaScript is only meant for enhancing behavior and performing client-side manipulations. It was never meant to handle complex business logic or hefty calculations. So, you have to split business logic between your server-side code and a client-side script file. Another possible problem is potentially having to duplicate logic in both your server-side code and your client-side scripts.
AJAX will not work in all web browsers. As its name suggests, AJAX requires JavaScript. This alone means that AJAX applications will not work in web browsers and devices that do not support JavaScript. For this reason it is not accessible to many typical Web users.
The current solution to these problems is to either provide a non-AJAX alternative to your application or to allow your AJAX application to continue to function if JavaScript and XMLHttpRequest are not supported. The general strategy here is to start by creating a page that works like a normal site-processing information on page loads and refreshes. Then, if JavaScript is enabled, we have our scripts bypass this normal functionality and replace it with sweet Ajax functionality.
