[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
• 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>
• Message-ID: <4D9AFC88.2060200@nokia.com>

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).
    http://www.w3.org/Bugs/Public/show_bug.cgi?id=11834

2. WebSocket protocol update time
    http://www.w3.org/Bugs/Public/show_bug.cgi?id=12102

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? ...
    http://www.w3.org/Bugs/Public/show_bug.cgi?id=10213

-Art Barstow

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