W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

[websockets] Binary support changes

From: Adrian Bateman <adrianba@microsoft.com>
Date: Fri, 27 May 2011 22:55:03 +0000
To: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
Message-ID: <104E6B5B6535E849970CDFBB1C5216EB432EB513@TK5EX14MBXC136.redmond.corp.microsoft.com>
I'm pleased to see the changes in the WebSockets API for binary message support.
I'm a little confused by this text:

    When a WebSocket object is created, its binaryType IDL attribute must
    be set to the Blob interface object associated with the same global
    object as the WebSocket constructor used to create the WebSocket object.
    On getting, it must return the last value it was set to. On setting, if
    the new value is either the Blob or ArrayBuffer interface object
    associated with the same global object as the WebSocket constructor used
    to create the WebSocket object, then set the IDL attribute to this new
    value. Otherwise, throw a NOT_SUPPORTED_ERR exception.

I don't entirely follow what this is saying but we'd prefer the binaryType to be
a DOMString in the same fashion that the responseType is in XHR2. Is there a reason
for this to be an object? We'd prefer consistency.

Thanks,

Adrian.
Received on Friday, 27 May 2011 22:55:31 GMT

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