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

[whatwg] Issues with Web Sockets API

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 4 Sep 2009 01:46:15 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0909040145010.6775@hixie.dreamhostps.com>
On Thu, 13 Aug 2009, Alexey Proskuryakov wrote:
> 13.08.2009, ? 4:42, Ian Hickson ???????(?):
> > > 
> > > 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().
> 
> Why not? My understanding is that it can take arbitrary amount of time - 
> the server can choose not to close its side of connection for years, and 
> to send data over it.

It's unrelated to the server.

You call close(), the UA closes the connection, thus the connection is 
closed, which causes the UA to fire an event.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 3 September 2009 18:46:15 UTC

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