W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

Re: [websockets] ArrayBuffer added back to the ED

From: Arthur Barstow <art.barstow@nokia.com>
Date: Sat, 28 Jul 2012 08:21:42 -0400
Message-ID: <5013D956.3060508@nokia.com>
To: ext Takashi Toyoshima <toyoshim@chromium.org>, Adrian Bateman <adrianba@microsoft.com>, Alexey Proskuryakov <ap@webkit.org>, Anne van Kesteren <annevk@annevk.nl>, "Edward O'Connor" <eoconnor@apple.com>, yutak@chromium.org, Glenn Maynard <glenn@zewt.org>
CC: public-webapps <public-webapps@w3.org>, Ian Hickson <ian@hixie.ch>
On 7/26/12 8:41 AM, ext Takashi Toyoshima wrote:
> Hi,
>
> Thank you for handling this topic.
> I support this change [r1.272] is applied to v1 spec.

OK, thanks for being clear.

Anyone else, especially those that added a comment to bug 17263, have 
any feedback on whether or not we should block the WebSocket API CR and 
first publish a new LC with Hixie's fix for this bug?

In the absence of any additional feedback, I will start a new CfC for LC 
(and stop the request to publish a CR).

-Thanks, AB


> On Thu, Jul 26, 2012 at 5:01 AM, Arthur Barstow <art.barstow@nokia.com> wrote:
>> Hi All,
>>
>> Earlier today, Hixie added ArrayBuffer back to the WebSocket API ED (see
>> [r1.272]) as requested in bug [17263] which ATM is Resolved/WontFix.
>>
>> Since the CfC to move this spec to CR passed on July 18 (but the CR has not
>> yet been published), I would appreciate it you would please Raise Your Hand
>> if you support this fix for v1.
>>
>> If there is consensus for this fix to be included in v1, it would mean the
>> next step on the REC track would be to return the spec to LCWD.
>>
>> -Thanks, AB
>>
>> [r1.272]
>> <http://dev.w3.org/cvsweb/html5/websockets/Overview.html.diff?r1=1.271;r2=1.272;f=h>
>> [17263] <https://www.w3.org/Bugs/Public/show_bug.cgi?id=17263>
>>
>>
Received on Saturday, 28 July 2012 12:22:24 GMT

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