noVNC/include
Joel Martin ac7bdbc22f web-socket-js (issue #37): close() when connecting
Filed this issue for this bug:
http://github.com/gimite/web-socket-js/issues/issue/37

Right now the close() call only calls __flash.close() if readyState is OPEN.
But it should really call close any time that readyState is not CLOSED or
CLOSING.

The case I ran into is when I want to do the following:
1. make a test connection
2. tell the server to setup for a connection
3. connect again

I call close on the test connection, but since it is ignored when CONNECTING,
it eventually times out with a error. But by that time I have already issued a
new connection, it causes the new connection to fail. close() should cancel
CONNECTING state too.
2010-09-11 13:52:49 -05:00
..
web-socket-js web-socket-js (issue #37): close() when connecting 2010-09-11 13:52:49 -05:00
base64.js JSLint. 2010-09-08 10:11:11 -05:00
black.css API changes. Client cursor and settings menu. 2010-07-21 20:34:23 -05:00
canvas.js License header cleanup. 2010-09-08 15:06:34 -05:00
default_controls.js License header cleanup. 2010-09-08 15:06:34 -05:00
des.js JSLint. 2010-09-08 10:11:11 -05:00
plain.css API changes. Client cursor and settings menu. 2010-07-21 20:34:23 -05:00
rfb.js License header cleanup. 2010-09-08 15:06:34 -05:00
util.js License header cleanup. 2010-09-08 15:06:34 -05:00
vnc.js License header cleanup. 2010-09-08 15:06:34 -05:00