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

[whatwg] Issues with Web Sockets API

From: Drew Wilson <atwilson@google.com>
Date: Fri, 26 Jun 2009 09:46:08 -0700
Message-ID: <f965ae410906260946x4ba99dear742a828d0b266342@mail.gmail.com>
On Fri, Jun 26, 2009 at 9:18 AM, James Robinson <jamesr at google.com> wrote:

> However, users can't usefully check the readyState to see if the WebSocket
> is still open because there are not and cannot be any
> synchronization guarantees about when the WebSocket may close.
>
>
Is this true? Based on our prior discussion surrounding cookies, it seems
like as a general rule we try to keep state from changing dynamically while
JS code is executing for exactly these reasons.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090626/9c2fca49/attachment.htm>
Received on Friday, 26 June 2009 09:46:08 UTC

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