W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2011

[whatwg] Websockets Client API

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 21 Feb 2011 11:57:59 +1300
Message-ID: <AANLkTikAPTeMLupK70hDcw1hZiV8Ta800-dY1VoDf2cR@mail.gmail.com>
On Mon, Feb 21, 2011 at 11:38 AM, Toni Ruottu <toni.ruottu at iki.fi> wrote:

> I believed that the browser is expected to somehow magically delay the
> events until a callback has been registered. At least that is how it
> seems to work at the moment. The specification could be clearer about
> this.

It's not magic, the spec is perfectly clear. The language about "queuing a
task" ensures that any callback events fire after the current task (e.g. the
script event handler that created the Websocket connection) has run to

"Now the Bereans were of more noble character than the Thessalonians, for
they received the message with great eagerness and examined the Scriptures
every day to see if what Paul said was true." [Acts 17:11]
Received on Sunday, 20 February 2011 14:57:59 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC