There were workarounds of course. I've seen "AJAX" applications since at least 2000. Instead of an ActiveX object, or some other non-standard browser extension, it was a scripted Applet in charge of dynamically calling the server, and it worked well. Of course at that time, the were reams of code for handling the cross-browser compatibility, but it was perfectly doable. The AJAX acronym adds one more thing: XML. Whether it's useful or not is a debatable question. Most of the time you just want to retrieve snippets of HTML or a list of value, and the XML overhead can be questionned. Of course we're not talking about some of Hummer-likes technique like XML Schema validation.
Matt Raible references the DWR project (hosted on the irritant java.net, which forces the use of SSL), which has the good idea (or "innovating idea" with an AJAX certified vocabulary) to provide boilerplate code on the client side as well as on the server side. It's probably worth a good try.
une réaction
1 De Guillaume Laforge - 29/04/2005, 07:38
Yeah, Ajax, that's funny, but for me it also meant two things: a famous football (soccer) team and a famous cleaning products brand. I wanted to blog about that but didn't dare.
I've also seen and worked on applications using XMLHttpRequest for several years. We used it to save/update forms on the fly without a page refresh, and for other clever search features (a la Google Suggest). So that's really nothing new. That's just in the fashion these days :-)