W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

[XHR2] responseType / response / overrideMimeType proposal

From: Anne van Kesteren <annevk@opera.com>
Date: Mon, 29 Nov 2010 18:21:44 +0100
To: "WebApps WG" <public-webapps@w3.org>
Message-ID: <op.vmxzuiea64w2qv@g223.guest-int.opera.com>
Before I write it out it would be nice to assess whether there is  
consensus on this. From the current draft, asBlob, responseBlob, and  
responseArrayBuffer are removed. response and responseType are added.

responseType can be set when the state is either OPENED or  
HEADERS_RECEIVED and must be set before send() is invoked for synchronous  
requests. When set at an inappropriate point it throws INVALID_STATE_ERR  
much like the other attributes. (This means responseType can be set during  
the request, specifically after all headers are available to the author so  
she/he can make an informed choice what to set responseType to.)

Depending on the type response either starts returning at LOADING or DONE.

overrideMimeType can be invoked whenever responseType can be set.

responseType has these constants:

   RESPONSE_DEFAULT
   RESPONSE_TEXT
   RESPONSE_DOCUMENT
   RESPONSE_BLOB
   RESPONSE_ARRAY_BUFFER

When set to anything but RESPONSE_DEFAULT responseText and responseXML  
will throw INVALID_STATE_ERR. When set to RESPONSE_DEFAULT response  
returns what responseText returns. (This seems mildly better than  
throwing, but I can be convinced to make it throw instead.)


-- 
Anne van Kesteren
http://annevankesteren.nl/
Received on Monday, 29 November 2010 17:22:17 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:42 GMT