[whatwg] Issues with Web Sockets API

Ian Hickson ian at hixie.ch
Thu Aug 13 04:42:41 PDT 2009

On Tue, 4 Aug 2009, Alexey Proskuryakov wrote:
> 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.

It won't be long after the close(). If the UA closes the connection, then 
the conditions under which "the Web Socket connection is closed" occurs 
will quickly come to be.

I've tried to make this a little clearer.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'

More information about the whatwg mailing list