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

[whatwg] Issues with Web Sockets API

From: Darin Fisher <darin@chromium.org>
Date: Fri, 26 Jun 2009 09:52:59 -0700
Message-ID: <bd8f24d20906260952la72aefeu9b0d907b6a105131@mail.gmail.com>
On Fri, Jun 26, 2009 at 9:46 AM, Drew Wilson <atwilson at google.com> wrote:

>
> 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.



I think this is a very different beast.  The state of a network connection
may change asynchronously whether we like it or not.  Unlike "who" may
access cookies or local storage, the state of the network connection is not
something we solely control.

-Darin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090626/0daab0f6/attachment.htm>
Received on Friday, 26 June 2009 09:52:59 UTC

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