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

[websockets] What needs to be done before the spec is LC ready?

From: Arthur Barstow <art.barstow@nokia.com>
Date: Tue, 05 Apr 2011 07:27:04 -0400
Message-ID: <4D9AFC88.2060200@nokia.com>
To: public-webapps <public-webapps@w3.org>
CC: Peter Saint-Andre <stpeter@stpeter.im>, Gabriel Montenegro <Gabriel.Montenegro@microsoft.com>, Salvatore Loreto <salvatore.loreto@ericsson.com>, Mark Nottingham <mnot@mnot.net>
Hi All,

What needs to be done before the WebSocket API is LC ready?

Bugzilla has three open bugs for this spec:

1. API for send/receive of binary data? Current IETF protocol drafts 
have binary type. Consider typed arrays (ArrayBuffer).

2. WebSocket protocol update time

3. The definition of "absolute url" makes https:foo not an absolute url, 
since its behavior depends on whether the base is https: or not. Is that 
desired? ...

-Art Barstow
Received on Tuesday, 5 April 2011 11:27:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:18 UTC