Why Microsoft and Google are Cleaning Up With AJAX 443
OSS_ilation writes "Google uses it, and Microsoft is pursuing it, so there's a lot of hype and hubbub surrounding AJAX (Asynchronous JavaScript and XML). AJAX brings together some hot properties, JavaScript, HTML/DHTML and HTML, according to Julie Hanna Farris, founder of Scalix, a Linux-based, e-mail systems vendor. Scalix is using AJAX in Scalix Web Access (SWA), a Web-delivered, e-mail application. AJAX enables advanced features like drag 'n drop, dropdown menus and faster performance capabilities, which are now making their way into Web applications, she said. These kinds of capabilities represent a significant leap in the advancement of Web apps."
Microsoft pursuing it??? (Score:2, Informative)
Re:What is ? (Score:3, Informative)
-Rick
Re:What is ? (Score:3, Informative)
Here's an overview. [asp.net]
Re:What my dog hears (Score:3, Informative)
Be Careful (Score:3, Informative)
Of course, you usually don't know if a page is using XMLHTTPRequest in a hidden frame unless you look really hard, so I guess the bottom line is never type anything on a web page you don't want the world to see. On the other hand, AFAIK (which doesn't mean much) this hasn't shown up in practice, so maybe it isn't that big a deal.
Re:AAX??? (Score:4, Informative)
Re:Where? ajaxian.com (Score:4, Informative)
Re:Funny thing is... (Score:4, Informative)
Microsoft invented XMLHttpRequest because before that people were using tiny little java applets to accomplish the same thing. In fact the original version of remote scripting in IE also used a java applet. When MS decided that java was the enemy they figured a way to do it without java.
I for one see no need for AJAX, it's better to just write java applications or even applets (or thinlets).
List of websites using Ajax (Score:5, Informative)
Re:Incoming data (Score:5, Informative)
Try this:
#!/usr/bin/perl
print "Content-type: text/plain\n\n";
$|=1;
(print '.'),sleep 1 while 1;
2. With XMLHttpRequest:
var req = new XMLHttpRequest();
req.multipart=1;
and the server-side part uses content-type: multipart/x-mixed-replace
Re:AJAX: Almost Just like an Application! (Score:1, Informative)
Accessibility (Score:5, Informative)
So you can't use it in software that might be sold to, for example US Government customers -- no national laboratories, no NASA, etc.
UNLESS -- you write your own accessibility aids and write your own UI framework that compiles into both an AJAX version and a web accessible version.
That's a tall order. However, there is help.
You can write your web pages in HTML with XForms and let XForms handle the dynamic page aspects, and then offer up the HTML+XForms as the accessible version. (See the DHTML Accessibility Roadmap [w3.org].)
Everything that the AJAX cloud of applications does with the XMLHTTP object and updating the DOM on the fly to display choices can be done with XForms.
Then, you can use one of these mechanisms to convert the server-side XHTML+XForms file into AJAX:
If you want to serve up the XHTML+XForms directly, and not rely on any AJAX technologies, try these:
So, try them out, and see how much easier it is to write accessible code and properly separate your data and presentation layers when you use XHTML, CSS, and XForms. Then, choose a middleware solution or a browser-based solution and go forward knowing that you can meet architectural requirements without getting bogged down in JavaScript toolkits.
Re:AAX??? (Score:3, Informative)
Existing APAX solutions use py2js so you write client code in python which is translated to javascript automagically.
See, e.g., Crackajax (or use plain py2js if you don't want a big framework).
http://www.aminus.org/blogs/index.php/phunt/2005/
I think TurboGears has something similar.
Re:Ditch Javascript (Score:3, Informative)
Javascript+XUL is very powerful. Consider that the entire Firefox front end is written in XUL and Javascript. You can use AJAX with XUL, BTW.
-matthew
Re:real reason why (Score:5, Informative)
Saying that AJAX will allow one to deliver desktop quality applications is like saying central heating will turn a mobile home into a mansion.
-matthew
Re:Accessibility (Score:2, Informative)
Re:Accessibility (Score:5, Informative)
This irritates me. This is not true. And yet moderators without a clue have pushed it up to +5, Informative. And any newbie web developers who read this are going to think that they have to choose between AJAX and accessibility. Some of them are going to choose AJAX and not bother with accessibility. If your post had been down at -1, Wrong, they might not get that impression, and would go on to write accessible AJAX web applications.
You don't have to choose. You don't have to write "UI frameworks" that you have to "compile". That's nonsense. What you do is you write the non-AJAX version, and then you add the AJAX as an optional extra. When people have Javascript turned off, they get the basic version seamlessly. Perfectly accessible, none of the complicated nonsense you claim is necessary.
Please stop propogating this myth. If you want to promote your favourite technologies, then by all means do so, but don't lie about the alternatives to make them look bad.
Re:real reason why (Score:3, Informative)
XUL [xulplanet.com] provides both. AND you can use it with AJAX. But, alas, it only works with Mozilla based browers.
-matthew
Re:Funny thing is... (Score:2, Informative)
I'm willing to give MS a big credit in this, however, since they did to XmlHttpRequest first, as well as their remote scripting, which makes easier tie ins on the server-side... their Atlas framework falls a little short of Ajax.Net's interfaces though.
Bullshit (Score:0, Informative)
"Your web browser is not fully supported by Google"
There's no "basic version seamlessly" there.
Re:Funny thing is... (Score:2, Informative)
There should be no denying, MS lead the development of HTML into DHTML into what is basically refered to AJAX today. It might be that W3C defined certain things, but the "violation" of those definitions by MS (which many times W3C adopted) is the reason AJAX exists today.
Trace back the features you like today about AJAX and they all come down to MS features extending what was at the time the standard of web.