Skip to content
Snippets Groups Projects
Select Git revision
  • master default
  • develop
  • issue/144/improvement
  • issue/140/improvement
  • issue/143/improvement
  • issue/142/improvement
  • issue/136/improvement
  • refactor/es6-module-loader
  • gh-pages
  • stable/v0.6
  • visualhint
  • tmp-branch/throw-error-on-error
  • novnc-legacy
  • xpra
  • app
  • html5-test
  • v0.6.2
  • v0.6.1
  • v0.6.0
  • v0.5.1
  • v0.5
  • v0.4
  • v0.3
  • v0.2
  • v0.1
25 results

web-socket-js

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    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
    History
    Name Last commit Last update
    ..