-
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.
a93c9555
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| bridge | ||
| com | ||
| WebSocket.as | ||
| WebSocketMain.as | ||
| WebSocketMain.swf | ||
| WebSocketMessageEvent.as | ||
| WebSocketStateEvent.as |