Repository navigation
Support for Node v0.10.x #22
Description
This library works great for socket.io v0.9 and node v0.8.x, but I've upgraded my node version and found that socket.io will stall after "handshake authorized".
In testing the demo code on Node v0.10.x, sending data over websockets appears to show that the data is being received by the server, but not as a message. Instead it appears in the debug as the following:
debug - flashsocket received data packet 3:::[Message goes here]
The client, on other hand, does not appear to receive anything from the server.
Any ideas why this might be the case or how one might go about solving this issue?
Activity
mayuan97 commentedon Aug 3, 2013
I met the same issue with node v0.10.x. Additional info, if I use flash builder to execute the client code, everything goes well. But when I put the compiled swf file to the public folder of express, flash socket seems stuck.
I suspect it's an authorization related problem, because executing with flash builder, web browser will not load the cross-domain file and other related files.
simb commentedon Aug 5, 2013
Interesting. I know that you specifically have to turn on flash in the server config now. Do you also have to expressly enable the flash security server? My guess is that the internal security that used to happen automatically is now opt in for 0.10
funseiki commentedon Aug 5, 2013
Hmm, I think it might have to do with Chrome/Firefox (as well as potentially needing to opt-in - haven't tried this yet). From the wiki:
simb commentedon Aug 5, 2013
This actually only matters if you are using the socket.io js client. If you are doing it in Flash/AIR then its using its own networking subsystem.
At least that was how it was last time I had to fight with this.
The 1.0 release is a pretty big departure from the 0.9 and previous architecture. So its entirely possible that I may have to write something new to make it work.
funseiki commentedon Aug 5, 2013
Oh ok.
Maybe I'm wrong, but it looks like it has more to do with some of the lower level changes in Node's 0.10.x as opposed to socket.io. Keeping both socket.io versions (0.9.16) the same, but upgrading Node reproduces the issue.
simb commentedon Aug 5, 2013
Oh, sorry I missunderstood what the 0.10 version was referencing. I was talking about the socket.io version 1.0 and its move to engine.io. I would not expect things to fail just by updating node. And if that is true its something that will need to be addressed for sure.
I totally misread that and I am very sorry. I'll see if I can get an environment setup to test this and confirm whats going wrong.
funseiki commentedon Aug 5, 2013
Ah yeah, no worries - glad I could clarify. Thanks for looking into this (and also for the AS3 library!).
Shrill commentedon May 6, 2014
I'm getting the same issue described by funseiki and mayuan97. Running Node 0.10.x and socket.io 0.9.16. Works with Adobe AIR and local standalone Flash Players, but stalled after the "handshake authorized" message when running Flash Player in the browser.
Did you guys find a fix in the end?