W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2009

[whatwg] Thread to run Web Socket feedback from the protocol ?

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 9 Dec 2009 10:06:04 -0800
Message-ID: <63df84f0912091006w4dbae18fp685b13f4402c38ba@mail.gmail.com>
On Wed, Dec 9, 2009 at 9:53 AM, Ian Hickson <ian at hixie.ch> wrote:
> On Wed, 9 Dec 2009, Jonas Sicking wrote:
>> On Wed, Dec 9, 2009 at 9:34 AM, Ian Hickson <ian at hixie.ch> wrote:
>> > On Wed, 9 Dec 2009, Alexey Proskuryakov wrote:
>> >>
>> >> Data from network is only processed as an event loop task
>> >
>> > I do not believe this is accurate. It certainly isn't what is specced.
>>
>> In XMLHttpRequest this is certainly accurate. You will never see
>> .responseText changing in the middle of an execution thread, it's
>> always changed in response of a task run from the event loop.
>
> Sure. From the spec's point of view, a task is queued by the background
> network thread to update the responseText attribute. (I haven't checked if
> that's how Anne actually specced it, but something to that effect is
> needed, otherwise you can see the attribute changing from under you in a
> running script.)
>
> I'm absolutely fine with changing WebSocket to change readyState as part
> of the same task that dispatches the event

Yes, that is what I think the spec should say.

/ Jonas
Received on Wednesday, 9 December 2009 10:06:04 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:54 UTC