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

[whatwg] Issues with Web Sockets API

From: Drew Wilson <atwilson@google.com>
Date: Wed, 29 Jul 2009 12:05:16 -0700
Message-ID: <f965ae410907291205k7f124a2bu739b20a2bb99a06c@mail.gmail.com>
On Wed, Jul 29, 2009 at 1:33 AM, Ian Hickson <ian at hixie.ch> wrote:
>
>
> Yes. But that's the case anyway -- events are asynchronous, so consider
> the case of receiving two messages. Both are queued up, then eventually
> the first is dispatched. If in response to that you close the connection,
> that doesn't stop the second being dispatched, since it was already queued
> up.
>

I'd note that this conforms to the behavior of MessagePorts - close
disentangles the ports, but already-received/queued messages are still
delivered.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090729/3e001da0/attachment.htm>
Received on Wednesday, 29 July 2009 12:05:16 UTC

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