Issues in Ajax based applications

Posted by Sinuhe on Stack Overflow See other posts from Stack Overflow or by Sinuhe
Published on 2010-05-04T11:30:31Z Indexed on 2010/05/04 11:38 UTC
Read the original article Hit count: 232

I'm very interested in developing Ajax based applications. This is, loading almost all of the content of the application via XMLHttpRequest, instead of only some combos and widgets. But if I try to do this form scratch, soon I find some problems without an easy solution. I wonder if there is some framework (both client and server side) to deal with this issues. As far as I know, there isn't (but I've searched mainly in Java world). So I am seriously thinking of doing my own framework, at least for my projects.

Therefore, in this question I ask for several things. First, the possible problems of an ajax based development. Then, I'm looking for some framework or utility in order to deal with them. Finally, if there is no framework available, what features must it have.

Here are the issues I thought:

1 - JavaScript must be enabled. Security paranoia isn't the only problem: a lot of mobile devices couldn't use the application, too.

2 - Sometimes you need to update more than one DIV (e.g. main content, menu and breadcrumbs).

3 - Unknown response type: when you make an Ajax call, you set the callback function too, usually specifying if expected response is a javascript object or in which DIV put the result. But this fails when you get another type of response: for example when the session has expired and the user must log in again.

4 - Browser's refresh, back and forward buttons can be a real pain. User will expect different behaviors depending on the situation.

5 - When search engines indexes a site, only follow links. Thus, content load by Ajax won't "exist" for who doesn't know about it yet.

6 - Users can ask for open a link in a different window/tab.

7 - Address bar doesn't show the "real" page you are in. So, you can't copy the location and send it to a friend or bookmark the page.

8 - If you want to monetize the site, you can put some advertisings. As you don't refresh entire page and you want to change the ad after some time, you have to refresh only the DIV where the ad is. But this can violate the Terms and Conditions of your ad service. In fact, it can go against AdSense TOS.

9 - When you refresh an entire page, all JavaScript gets "cleaned". But in Ajax calls, all JavaScript objects will remain.

10 - You can't easily change your CSS properties.

© Stack Overflow or respective owner

Related posts about AJAX

Related posts about web-development