Firefox websockets

[thenwithexpandedwingshesteershisflight]

Hi, I know I've already asked about this, but I've got to make it work
soon & I can't see what's wrong. I can't get Firefox 10.0.1's
MozWebSocket to connect with Aleph, the readystate is always 0
(connecting), whereas Chrome works beautifully. I have tested
MozWebSocket with other servers, for instance var w= new
MozWebSocket("ws://isr.servequake.com/echo"); connects.

[Zach Tellman]

I'll take a look at this today.

[Zach Tellman]

A fix has been checked into 0.2.1-alpha2-SNAPSHOT.

[thenwithexpandedwingshesteershisflight]

it works! thankyou, this means a lot - cheers

[Daniel E. Renfer]

I can confirm that it is also working for me again, although I can't tell to what extent it was broken for me before as I just today discovered that Nginx doesn't properly proxy all the needed information for websockets and I am temporarily having the websocket connection go to my aleph port (8085 in my case) directly.

I would also like to point out this project that I just found today. https://github.com/gimite/web-socket-js It takes care of the cross browser support and allows Firefox and Chrome to connect. (haven't tried any other browsers yet). This library will even allow you to use the Google Closure Library version of Websocket via Clojurescript. (you'll need to package the updated goog.jar and require that in your project)

So thanks again, Zach. Now it's time to do some websocket programming. :)

[thenwithexpandedwingshesteershisflight]

I have Chrome and Firefox communicating via Aleph through websockets
in a fully Clojurescript project. I had to patch goog.jar to include
the dependencies and websockets.js, and I had to wrap closure's
WebSocket class to detect firefox and change the wrapped factory to
MozWebSocket from WebSocket.

I considered using websocketjs, but since I didn't care about 100%
compatibility I didn't want to get Flash involved. Chrome and Firefox
is enough compatibility for me.

On Feb 24, 4:57 am, "Daniel E. Renfer" <duck112...@gmail.com> wrote:
> I can confirm that it is also working for me again, although I can't
> tell to what extent it was broken for me before as I just today
> discovered that Nginx doesn't properly proxy all the needed information
> for websockets and I am temporarily having the websocket connection go
> to my aleph port (8085 in my case) directly.
>

> I would also like to point out this project that I just found today.https://github.com/gimite/web-socket-jsIt takes care of the cross