I do beg to differ regarding the use Asynchronous XMLHttpRequest. Sure, it's just a speed-up thing, and when I get my spanking new 10GigE fibre link and SiCoretex SC5832 5,832 processor system (seriously, check out their web site), I'll live with page re-draws. But until then, judicious use makes sense. Although we have probably all experienced poor and useless implementations that break the back button, among other things.
Unless you are doing something highly dynamic like google maps, I think a prudent strategy is to start with conventional strategies and only then layer on Asynchronous XMLHttpRequest where it truly makes sense and the consequences are fully understood. Cliff -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of csnyder Sent: Friday, November 10, 2006 12:32 PM To: NYPHP Talk Subject: Re: [nyphp-talk] So who's using Ajax anway? On 11/9/06, David Mintz <[EMAIL PROTECTED]> wrote: > > OK then, it's all settled: the X in AJAX actually stands for "whatever." Heh. I don't use AJAX anymore. 1) XML is so bloated and slow compared to JSON. Just because Java likes it doesn't mean other languages do. 2) The whole Asynchronous XMLHttpRequest thing breaks the web paradigm and accessibility in interesting ways. I'll take form submission to a hidden iframe any day. Maybe it's time to stand up for DHTML again. AJAX is like Flash, it's pretty but it breaks shit. DHTML still works the way it always has, we just happen to understand it better now. -- Chris Snyder http://chxo.com/ _______________________________________________ New York PHP Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
