Samuel Mannehed 9f909d9b46 Don't wait for websocket closes on failure ...

RFB._fail() can be called at any time in any state, it is not certain
that we will get a close event on the socket since the socket might not
be open. This caused us to hit the disconnect timeout in such cases.

Fixes issue #678

2016-11-10 15:17:37 +01:00

..

input

Merge pull request #689 from ossman/keysym

2016-11-10 09:36:43 +01:00

base64.js

Enable noVNC to become Browserifiable

2016-09-16 15:49:51 -04:00

des.js

Enable noVNC to become Browserifiable

2016-09-16 15:49:51 -04:00

display.js

Don't allow more than one pending update

2016-10-24 14:42:45 +02:00

inflator.js

Enable noVNC to become Browserifiable

2016-09-16 15:49:51 -04:00

inflator.mod.js

Enable noVNC to become Browserifiable

2016-09-16 15:49:51 -04:00

rfb.js

Don't wait for websocket closes on failure

2016-11-10 15:17:37 +01:00

util.js

Added Greek translation

2016-10-28 21:22:25 +03:00

websock.js

Enable noVNC to become Browserifiable

2016-09-16 15:49:51 -04:00