Hi,
The latest editor's draft of the XMLHttpRequest can be found here:
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/Overview.html?content-type=text/html;%20charset=utf-8
In addition there's also a disposition of comments document for the first
Last Call:
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/disposition-of-comments
There has also been offlist feedback and I've tried addressing the hundred
of so outstanding comments the WHATWG version of this specification had.
Given that there've been quite some changes in response to feedback we
need to have another Last Call. Here's an overview of the changes:
* For compatibility reasons the character encoding detection
for decoding responseText has been changed.
* text/xsl has been added as a MIME type that causes
responseXML to return a Document object (if the resource
can indeed be parsed according to the XML specfications.)
Again, for compatibility reasons.
* Five constants have been added to the specification for
readyState for consistency with other DOM specifications.
* Most members are now defined as algorithms which makes the
result of a method more clear (hopefully) and also helped
me fixing several issues.
* The setRequestHeader definition has been changed to match
what Internet Explorer and Safari (WebKit) do. That is, the
method always appends to an header. No more "magical"
headers. A future specification might introduce methods to
inspect already set headers and maybe replace headers as
well.
All other changes have been editorial as far as I can tell. You can view
more detailed change logs of the specification here:
http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest/Overview.html
Please let me know if I missed anything, such as making technical or
editorial mistakes or failing to add your name to the list of
acknowledgements.
Kind regards,
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
