- From: Óscar Toledo G. <uno@biyubi.com>
- Date: Mon, 17 Jul 2006 17:14:40 GMT
- To: public-webapi@w3.org
After reading the draft, appears as setRequestHeader must ignore Content-MD5, User-Agent and From headers, as Content-MD5 can be only calculated after the send method has generated the data, and User-Agent and From are generally provided by the UA. Also generating exceptions on reading status and statusText, is a little awkward, I think that zero and empty string are more sensible selections. Other suggestions, the send method can include a second argument to indicate the desired timeout in milliseconds, to generate an event, would be better than setTimeout, as the event would not be generated if the answer comes first or the onerror handler exists and it is invoked first. The onerror event is necessary to detect a failed request (by example: server not responding HTTP connection), so is worth to have it into the draft, along with onload. Other alternative would be a special status 5 (Request error) for readyState. In the responseXML description, the draft could say something like: "An UA with a HTML implementation, may support additionally text/html, the Document node may have properties related to DOM HTML.". Truly Óscar Toledo G. http://www.biyubi.com/
Received on Tuesday, 18 July 2006 02:12:16 UTC