W3C home > Mailing lists > Public > public-webapi@w3.org > April 2008

Re: [XMLHttpRequest] Last Call

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 16 Apr 2008 20:35:34 -0700
To: Kris Zyp <kris@sitepen.com>
Message-Id: <55EEC172-3BAD-4CAE-BD03-50693903A9E2@apple.com>
Cc: "Web API WG (public)" <public-webapi@w3.org>, Anne van Kesteren <annevk@opera.com>


On Apr 16, 2008, at 7:50 PM, Kris Zyp wrote:

>
> We still do not have anyway to advice user agents of long-lived  
> responses in order to avoid the problem of indefinitely queued  
> pipelined requests/responses. With both pipelining and long-lived  
> responses becoming more common, this seems to be an envitable  
> problem. It doesn't seem acceptable to simply ignore this issue. I  
> am not asking for anything increasing the XHR implementation burden,  
> simply a standard way of advising so that authors and user agents  
> can communicate, so user agents have an approach for implementing  
> proper delegation of pipelined requests when users start complaining  
> of problems.

I think this would be more appropriate to deal with in XHR2, since we  
don't have a settled design for this feature and XHR1 is already way  
behind schedule.

  - Maciej

>
> Thank you,
> Kris
>
> ----- Original Message ----- From: "Anne van Kesteren" <annevk@opera.com 
> >
> To: "Web API WG (public)" <public-webapi@w3.org>
> Sent: Tuesday, April 15, 2008 12:40 PM
> Subject: [XMLHttpRequest] Last Call
>
>
>>
>> Hi,
>>
>> The Web API WG resolved yesterday to publish a Last Call Working  
>> Draft of The XMLHttpRequest Object specification. Thanks to the  
>> webmasters at the W3C it was published earlier today. Last Call  
>> comments can be made until 2 June 2008. (Please don't comment about  
>> the "befor" typo there. My mistake.)
>>
>> The draft is located here:
>>
>>  http://www.w3.org/TR/2008/WD-XMLHttpRequest-20080415/
>>
>> This is a rough list of the changes since the last published draft:
>>
>>  * Removed dependency on DOM Level 3 Events
>>  * Removed dependency on Window Object 1.0
>>    (we already depended on HTML 5 so we could use that instead)
>>  * Clearly marked which HTTP methods are to raise SECURITY_ERR
>>  * Mention HttpOnly in the security section
>>  * Accept-Language is set conditionally
>>  * Requests using a GET method will not have an entity body
>>  * responseText can no longer return null
>>  * responseText and responseXML no longer throw
>>  * Headers starting with Sec- will raise
>>  * getResponseHeader() will return null for invalid headers
>>  * getAllResponseHeaderS() returns empty string in case of failure
>>
>> A more detailed log of these changes, including links to the actual  
>> text changes, is available from dev.w3.org, here:
>>
>>  http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest/Overview.html
>>
>> Happy times reviewing!
>>
>> Kind regards,
>>
>>
>> -- 
>> Anne van Kesteren
>> <http://annevankesteren.nl/>
>> <http://www.opera.com/>
>>
>
>
Received on Thursday, 17 April 2008 03:36:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 17 April 2008 03:36:16 GMT