This thread discusses the Content article: When Not to Use AJAX

I think it's rather more likely that browsers will have to adapt to AJAX by, for example, making an easy API for mutating the history list and setting the current bookmarkable location. Google Web Toolkit for example already has tricks to do this, but they shouldn't have to use tricks, it should be built in.

AJAX as a design concept just makes so much more sense than server-side pages. Push all the UI work to the client (which has untapped processing power waiting to be used), let your server handle only the initial page delivery and the data (the minimum set of information which absolutely requires the the server's special knowledge).

It's simply conceptually cleaner.

It's simply for those who understand. But that was impressive,<br><br>Post edited by: phil, at: 2006/12/28 09:30

Ajax is fairly cool but not very search engine friendly.
It should mainly be used to enhance a sites functionality as opposed to displaying text content.

Is a good technology but I not such a big fan,<br><br>Post edited by: dan, at: 2007/01/12 17:47

Apparently it has some security issues as well. http://darksat.x47.net/topic/509.0.html