- 11 Sep, 2010 1 commit
-
-
Joel Martin authored
Filed this bug about this issue: http://github.com/gimite/web-socket-js/issues#issue/35 To work around the flash "recursive call" problem, WebSocket.as has the onclose event disabled in the close() call and the javascript half of the close() call does the onclose() call instead. This is fine, but it needs to be asynchronous to act more like what happens with a normal WebSockets object. The current behavior is that the onclose() method is called inline (synchronously) when the close() is called and this inconsistency make state handling more difficult.
-
- 08 Sep, 2010 1 commit
-
-
Joel Martin authored
web-socket-js now has all the functionality and fixes needed for noVNC so remove the include/as3crypto_patched directory and the include/web-socket-js/flash-src directory (i.e. the sources for web-socket-js). This cleans up almost 3K from the include/ directory. Update to web-socket-js build based on upstream (gimite/web-socket-js) 9e766377188.
-
- 02 Jul, 2010 2 commits
-
-
Joel Martin authored
The problem is, you can't set WebSocket.__swfLocation before you load web_socket.js (because it creates the WebSocket global), but you also can't reliably set WebSocket.__swfLocation after because if you are doing dynamic script file includes then the onload (i.e. WebSocket.__initialize) may fire before you have a chance to set Websocket.__swfLocation.
-
Joel Martin authored
Bug fixes, restore RFC2817 proxy for non wss://, and handle new closing handshake from WebSockets 76.
-
- 01 Jul, 2010 3 commits
-
-
Joel Martin authored
Add message/state pollling in web-socket-js. Since Opera tends to drop message events, we can dramatically increase performance by polling every now for message event data. Also, add more direct calls to update readyState so that it's not missed when Opera drops events.
-
Joel Martin authored
When using web-socket-js, the onopen event may happen inline so the caller may not have time to set onopen before the event fires. In this case set a short timeout and try again. In particular this affects Opera most of the time. Also, to get around Opera event droppings, always read the readyState directly instead of relying on the local readyState variable to be correct (which it isn't if stateChange event were dropped).
-
Joel Martin authored
Instead of relying on FABridge AS -> JS event delivery, we just use the events to notify JS of pending data. The message handler then calls the AS readSocketData routine which sends back an array of the pending WebSocket frames. There is still a minor bug somewhere that happens after the first connect where the web-socket-js throws an "INVALID_STATE_ERR: Web Socket connection has not been established". But, Opera is now usable and we should be able to drop the packet sequence numbering and re-ordering code. Another minor issue to better support Opera is to move JS script includes to the <head> of the page instead of after the body.
-
- 24 Jun, 2010 2 commits
-
-
Joel Martin authored
-
Joel Martin authored
-
- 28 May, 2010 1 commit
-
-
Joel Martin authored
-
- 17 May, 2010 1 commit
-
-
Joel Martin authored
-
- 17 Apr, 2010 1 commit
-
-
Joel Martin authored
web-socket-js is a flash based WebSockets emulator. From: http://github.com/gimite/web-socket-js
-