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

[whatwg] Issues with Web Sockets API

From: Alexey Proskuryakov <ap@webkit.org>
Date: Tue, 04 Aug 2009 16:57:05 -0700
Message-ID: <71816B06-BD88-415D-8DB9-A789503F0EFE@webkit.org>

04.08.2009, ? 16:47, Ian Hickson ???????(?):

> The text "Closing the connection causes a close event to be fired  
> and the
> readyState attribute's value to change, as described below" is not
> normative (it has no "must"s in it). It's just letting you know that
> subsequent requirements as described lower in the spec do result in  
> that.
>
> Is there some way I can make that clearer?


A note explaining that the close event will be dispatched at server's  
discretion (or on subsequent connection timeout), potentially long  
time after close() is called, would likely make the intention clearer.

- WBR, Alexey Proskuryakov
Received on Tuesday, 4 August 2009 16:57:05 UTC

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