XHR on W3C

Who says the World Wide Web Consortium moves slowly? The Web APIs Working Group is moving forward and the first steps are available for perusal on the W3C site.

See for yourself: a working draft for the XMLHttpRequest object. That’s right: the proprietary Ajax technology is on its way to becoming a web standard.

I doff my hat in the general direction of Dean Jackson, Anne Van Kesteren and the other authors of this document. If you don’t share my enthusiasm and you have any suggestions for the XHR draft, please note the injunction at the bottom of the page:

Thanks to all those who have helped to improve this specification by sending suggestions and corrections. (Please, keep bugging us with your issues!)

Posted by Jeremy on Monday, April 10th, 2006 at 10:30pm


All these acronyms are so confusing. Ajax apparently means Asynchronous JavaScript and XML. PHP used to mean Personal Home Page, but then it got redefined. There ought to be some Naming Standards, so that acronyms like URL mean one thing and one thing only — either Uniform or Universal Resource Locator, but not both simultaneously.

# Posted by mindmaker on Wednesday, April 12th, 2006 at 10:57am

Personally, I never use the term Ajax as an acronym (note the lower-case spelling). It’s a very, very useful term, but quite an inaccurate acronym. AJAX the acronym (Asynchronous JavaScript and XML) doesn’t accurately describe Ajax the methodology.

XMLHttpRequest, on the other hand, is a perfectly valid technical term but it’s a bit long-winded. Hence my use of the abbreviation XHR in the title.

You’re right about the acronyms PHP and URL. Here’s another one: RSS.

# Posted by Jeremy Keith on Wednesday, April 12th, 2006 at 9:41pm

Sorry. Comments are closed.

April 2006

Recommended Reading

XML Subscribe

Grab the RSS feed for this blog.

JavaScript API

Grab the RSS feed of comments for this entry.