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

[websockets] Seeking comments on moving back to CR; deadline July 9

From: Arthur Barstow <art.barstow@nokia.com>
Date: Thu, 28 Jun 2012 23:52:10 -0400
Message-ID: <4FED266A.8070703@nokia.com>
To: "public-webapps (public-webapps@w3.org)" <public-webapps@w3.org>
Hi All,

Since this was a busy week for some group members and I will be offline 
for several days, let's extend the deadline for comments until July 9.

If you have any feedback, please reply by July 9.

-Thanks, Art

-------- Original Message --------
Subject:        [websockets] Seeking comments on moving back to CR; 
deadline June 28
Resent-Date:    Thu, 21 Jun 2012 14:29:06 +0000
Resent-From:    <public-webapps@w3.org><mailto:public-webapps@w3.org>
Date:   Thu, 21 Jun 2012 10:28:31 -0400
From:   ext Arthur Barstow 
To:     public-webapps <public-webapps@w3.org><mailto:public-webapps@w3.org>

Hi All,

I created a tracking document for the two comments and five bugs that
were submitted against the 24 May LCWD of Web Sockets (or in the
approximate time frame of that publication):

Below is my "take" on these bugs and comments. It would be good to get
this spec back to CR and hence closer toward the IP commitments that
will only be final when the spec reaches Recommendation.


* 17073 
- marked
as an Enhancement; don't include in the v1 CR

* 17224 
- this
looks like an Editorial bug to me as I stated in the bug. Assuming there
is consensus the text should be "unsolicited pongs", if Hixie can't fix
this before the v1 CR copy is created, I'll make this change in the v1 CR.

* 17262 
- Jonas'
view as expressed in
reasonable so I propose closing this with a resolution of WorksForMe.

* 17263 
send(ArrayBuffer), which was included in the December 2011 CR, has been
implemented and presumably must be supported by some browsers (e.g.
bc/legacy reasons). As such, it seems reasonable to fix this bug and
perhaps we could argue a new LCWD is not needed since it has already
been implemented.

* 17264 
- this
bug appears to be a rehash of bug 13104 which was Fixed in October 2011
so I propose closing this with a resolution of Duplicate.


* LC-1
The 28-May-2012 reply by Takeshi Yoshino notes this is a Chrome bug and
not a spec bug. The 1-June-2012 reply by Simon Pieters indicates the
Protocol spec needs to be updated. As such, I don't think any changes
are needed for v1 of the spec.

* LC-2
This is an editorial bug and is already captured in Bug 12510. Ideally,
this bug would be fixed before the v1 CR branch is created. However, if
Hixie can't fix it before then and if no one else creates an acceptable
patch for Hixie, I don't support blocking the v1 CR for this.

Please send all comments by June 28.

-Thanks, AB
Received on Friday, 29 June 2012 03:52:44 UTC

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