Linked by Eugenia Loli-Queru on Thu 22nd Sep 2005 22:35 UTC
Thread beginning with comment 35290
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
RE: Asynchronous Javascript
by gonzalo on Fri 23rd Sep 2005 06:00
in reply to "Asynchronous Javascript"
Google Maps also does something this article didn't mention. It uses XSLT.
A client-side XML dataset that is transformed into HTML nodes is a very powerful concept. (Potential memory leaks aside).
For the laggards Google even implemented an XSLT Processor in Javascript! (Safari and Opera). And made it available:
http://sourceforge.net/projects/goog-ajaxslt/
Event code in Javascript, datasets in XML and displayed using XSLT. Thats the power of AJAX.






Member since:
2005-07-06
XMLHttpRequest may have made it simpler. Google Maps may have made it popular. But Asynchronous Javascript calls existed and were used a long time before both of them. As for the XML part... not only is most of the times unneeded, but also many applications prefer to skip that bit for a (small) speed gain. But anyway, nice article as introduction to AJAX.
@jessta: "Wonderfully AJAX usage will be kept to a minimum."
Or not. Of course you shouldn't impose too much restrictions on your visitors if you have a public website and want it to be popular.
But if you can, you should use what is best for the experience. Take Google Maps, for example. Sure, you can have a reduced version for those who can use the full one, but the whole point of Google Maps is the interface (and arguably the published API they provide).