Slashdot Mirror


Building Richly Interactive Web Apps with Ajax

FalsePositives writes "Ajax: A New Approach to Web Applications (from Adaptive Path and via Jeffery Veen) introduces their experiences with what they are calling 'Ajax' as in 'Asynchronous JavaScript + XML' aka the XmlHttpRequest Object. It is used by Google (Google Maps, Google Suggest, Gmail), in Amazon's A9, and a few others (like the map of Switzerland spotted by Simon Willison). ... Is this 'The rise of the Weblication'?"

4 of 358 comments (clear)

  1. Java app by dfj225 · · Score: 5, Interesting

    Maybe I'm missing the point somewhere, but if you really want something on the web to feel like an app, why not make it a Java app that runs in the browser? With all the different browsers and how they each handle Javascript differently, I much rather write something in Java and know it will almost always work on different platforms. Anytime I have to do something in Javascript, it almost always feels like a hack. I can't imagine writing something like the stuff Google does in Javascript. Is there really an advantage to doing stuff this way over the Java way?

    --
    SIGFAULT
  2. Re:Also Check out Bits of News by pe1rxq · · Score: 5, Interesting

    Ajax isn't a technology... its a cute name for a bunch of existing technologies.

    Basicly they found that you could make webpages update themself without completly reloading if you trow a lot of buzzwords at it.

    You could do this a long time ago without xml....
    I did it a while ago for a database app.. The page contained a piece of javascript that was started when a input field changed. This triggered the loading of a external .js file that just happened to be a cgi script. This cgi script would do some database queries and generated some javascript code that would update all the other fields on the client.

    Jeroen

    --
    Secure messaging: http://quickmsg.vreeken.net/
  3. Outperforming Desktop apps by davetrainer · · Score: 4, Interesting

    Here is an article by John Udell that I found fascinating when it was published a few months ago. It discusses the quasi-rich-client architecture that Google cobbled together to bring us GMail. The really incredible part is that interfaces built on this architecture, consumed in the browser, outperform commercial desktop apps:

    "One of my favorite acid tests is address completion. When you begin typing an e-mail address, your mail program should immediately show you the matching addresses and then dynamically constrain the list as you continue to type. Outlook does poorly on this test; you have to type CTRL-K to invoke the address book in a separate window. OS X's Mail does address completion in situ, just as I expect. So does Gmail. And here's the shocker: Gmail does it faster."

    I appreciate AP's efforts to assign some greater precision and clarity to this architecture. Up until now, realistically, I figured I had to be tethered to .net/XAML, Mozilla/XUL, or something like Macromedia Flex.

  4. bad photos by clmensch · · Score: 4, Interesting

    Why do tech writers feel the narcissistic need to display photos of themselves next to their writings? That is probably the largest photo I've ever seen on one of these articles...and it's an awful photo at that. They obviously cut the baldness of his head off for a reason, and half the photo is of his black on black outfit.

    Their whole site reeks of late 90's marketspeak. Slightly interesting article, though.

    --
    There is no gravity...the earth just sucks.