There’s a lot of noise about AJAX recently, ranging from positive to negative to what’s the big deal?
It’s true that architecturally, AJAX is nothing new — basically, it’s just the old, pre-Web client-server model wrapped up in the browser using Javascript and XML. It’s also true that people were doing this kind of thing with Java applets or DHTML back in the late 1990s, avoiding the need to install custom client software on every workstation. So what’s the big deal? Think back to the late 1990s — these applications were horribly unstable. First, they were rarely cross-platform, or even cross-version — you had to (say) be running exactly the right version of MSIE under Windows with the right DLLs, or exactly the right version of Netscape and Java, even to start up the apps, and then they generally crashed before too long anyway. Web developers are excited about AJAX now because applications like GMail are actually working on just about everyone’s computer (*nix/Windows/MacOS, MSIE/Firefox/Opera/Safari), and they almost never crash. New ideas aren’t worth much on the web; it’s stable, running, cross-platform implementations that count. We’ve never had good, stable, platform-independent client-server before, period.
Moving past the specific technologies, though, what are the advantages of abandoning our traditional thin-client web model and going back to client-server? One of the most interesting will be the ability to do information aggregation while preserving privacy. Imagine, for example, that I’d like to see a single, consolidated view of all my finances — my stocks, bonds, bank accounts, retirement savings, and credit cards. Using a thin-client approach, I have to give some web site, somewhere, the ability to access all of my private financial information for me; using a client-server approach, my browser itself could go out and retrieve the information separately from each institution and then aggregate it right on my screen. I have all the advantages of a single view, without giving up any personal information.
Privacy is going to be a bigger and bigger deal on the web over the next decade: as technology gets even better at violating it, governments will come under pressure to pass more and more legislation, limiting what corporations are allowed to ask for and do. AJAX in particular, and the client-server model in general, gives us one way to respect privacy without giving up the advantages of information aggregation.
The RESTafarians should be happy as well, since this involves using the browser as an XML+REST client.
Pingback: Quoderat » Tech Fashions: What’s in a name?
Pingback: Craig’s Musings » Blog Archive » Scrubbing bubbles and other cures for the common thin client application