…e we didn't attach a handler for it doesn't indicate that it's not a valid event.
…. Updated WebSocketMain to implement IWebSocketWrapper. Created IWebSocketWrapper
…bSocketController to manage multiple instances. Created central ExternalInterface manager at flash-src/bridge/JSBridge.as
…o manage multiple instances. Created central ExternalInterface manager at flash-src/bridge/JSBridge.as
…in Flash interface, to keep order of all events and avoid recursive call error. Using setTimeout() for event callback to avoid recursive call error. Removing FABridge.EventsToCallLater. Hopefully setTimeout() above is more confident alternative.
…icyFile() has not been called. Renaming WebSocket.loadPolicyFile() to WebSocket.loadFlashPolicyFile(). WebSocket.loadFlashPolicyFile() now expects URL including xmlsocket://.
…anyway. Furthermore, explicitly setting the port to 843 will make flash retry port 843 three times before trying the destination port. Instead we expose a method to the api loadPolicyFile that can be used to set the location of the policy file.
… IE (depending of version/debugger), console object doesn't define log() and error() from newbamboo/web-socket-js@2776dcf
Patch by kanaka. http://github.com/gimite/web-socket-js/issues#issue/35
…ere it must not be.