W3C home > Mailing lists > Public > public-webapi@w3.org > June 2007

Re: [XMLHttpRequest] Change to SENT state

From: Stewart Brodie <stewart.brodie@antplc.com>
Date: Mon, 25 Jun 2007 13:25:36 +0100
To: public-webapi@w3.org
Message-ID: <1c34d0c6bb62e6d91b1b97d2c061e0bdae1ff231@localhost>

"Anne van Kesteren" <annevk@opera.com> wrote:

> Feedback from Microsoft pointed out that the SENT state is in fact the  
> state that indicates that all HTTP headers have been received and that  
> LOADING indicates that the first few bytes of the response entity body are
 
> in. As a result, I renamed SENT to HEADERS_RECEIVED in the editor's draft 

> and slightly changed the send() algorithm:
> 
>   
http://dev.w3.org/cvsweb/~checkout~/2006/webapi/XMLHttpRequest/Overview.html?content-type=text/html;%20charset=utf-8
>   
http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest/Overview.html.diff?r1=1.123&r2=1.124&f=h
> 
> Kind regards,

So now you get *three* events dispatched immediately one after the other
when doing a HEAD request.  Still, since the spec is just documenting IE's
behaviour, you don't have a choice, I suppose.

Are you going to change all the methods like getRequestHeader so that they
are now valid in state HEADERS_RECEIVED - it would be just bizarre to issue
an event saying that we've got the complete HTTP header and then prohibit
the reading of the HTTP status and headers until the entity body has started
arriving.


-- 
Stewart Brodie
Software Engineer
ANT Software Limited
Received on Monday, 25 June 2007 12:27:55 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:57 GMT