pros and cons
like dhtml
applications, ajax applications have to be tested rigorously to deal with the
quirks of different browsers. the advantage of using the technology, however, is
the speed at which an application runs and responds to user interaction.
some application
developers argue that ajax ignores a common web development technique of
separating presentation markup and code fragments (architectures such as
model-view-controller adhere to this philosophy). defenders of ajax state that
developers shouldn't be overly strict when using such architectures, and that
some code on an html page can be beneficial to the usability of a web
application, as long as this is not abused.
adoption of ajax
whilst it has existed for
some time, in early 2005 a number of seminal events have popularised the
technique. firstly, google used
asynchronous communication as a basis for prominent interactive applications
including
google groups,
google maps and
gmail.
secondly, the name ajax was coined in
ajax: a new approach for a new application , which quickly came into popular
use and helped raise consciousness of the technique.
there are now a rapidly
growing group of applications which use ajax as a method for improving web page
interactivity, in part due to the increasing number of application toolkits
(e.g. ruby on rails)
that allow programmers to easily implement it.
external links
ajax: a new approach to web applications,
by jesse james garrett. the original article which coined the term
ajax: two steps forward... two steps back?
by john reynolds.
ajax, promise or hype? by peter-paul
koch.
is ajax worth adopting? by harshad
oak.
ajax matters
case study of using ajax in a crm system
by espen antonsen.
