Hiroshi Ichikawa
Hiroshi Ichikawa
It looks like you use web-socket-ruby, not web-socket-js. Right?
Sorry to be so late. Hmm I haven't tried WSS myself, so I'm not sure why. Does it work fine with native WebSocket e.g., with Chrome?
We had a discussion about it, and we decided not to add binary support for web-socket-js: #89 In short: - We anyway need ArrayBuffer or Blob to implement binary API,...
Yeah, it should workaround the first issue, but the second issue remains.
What's wrong with Safari 5.1's WebSocket?
What kind of handshaking problem does it have? Do you know why WEB_SOCKET_FORCE_FLASH doesn't hep? Note that you need to set the variable _before_ loading web-socket-js. e.g. ``` WEB_SOCKET_FORCE_FLASH =...
Sorry for late. That's good point. Hopefully I will work on it in near future, but I'm also happy to accept pull request. Alternatively you can use em-httprequest which supports...
I'm not exactly sure why, but it seems you are using somewhat old version of the library, because it speaks old WebSocket protocol. It may be fixed by using the...
I think the article says that "WebSocket supports UTF-8 characters, so you don't need any encoding". This is true for web-socket-js too. Problem here is that, web-socket-js internally use encodeURIComponent/decodeURIComponent...
Thanks for the information. So far we still use Flash implementation for Firefox, and the issue is implementation of encodeURIComponent/decodeURIComponent, which I'm not sure is also fixed by the change....