-
Joel Martin authored
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.
ac7bdbc2
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
FABridge.js | ||
README.txt | ||
WebSocketMain.swf | ||
swfobject.js | ||
web_socket.js |