Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Web Socket Status #12

Closed
autotelicum opened this issue Nov 23, 2011 · 1 comment
Closed

Windows Web Socket Status #12

autotelicum opened this issue Nov 23, 2011 · 1 comment

Comments

@autotelicum
Copy link
Owner

Tested on Windows 7 (no service pack):

Safari 5.1.1 - No Issues. Use this browser if your normal browser fails. You do not have to set it as your default browser. If it is installed in the default location then the browser launcher in the prelude will start it.

Opera 11.52 - No issues. But web sockets have to be enabled manually according to the instructions in the prelude.

Chrome 15.0.874.121 m - Fail. Does not launch its user interface when started as a child process from node.

Firefox 4 - No issues, if enabled, also works on Windows XP.
Firefox 8.0.1 - Fail. Has switched to a mozilla specific MozWebSocket on the client side. Mozilla's back and forth on this is described here. The change breaks applications, that worked in their version 4 browser. Changing the client code to MozWebSocket will obviously not work in other browsers, so I am not changing the draft standard compliant code. Besides the server implementation does not implement protocol 10.

Internet Explorer - Fail. Does not implement web sockets in version 9 and below. Version 10 is untested because it currently requires Windows 8.

@autotelicum
Copy link
Owner Author

For a production application, have a look at http://socket.io/#browser-support and http://socket.io/#how-to-use

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant