UnitySocketIO icon indicating copy to clipboard operation
UnitySocketIO copied to clipboard

Complete incompatibility with new Socket.IO

Open CSEliot opened this issue 10 years ago • 4 comments

Unless i'm interpreting the example wrong, I have:

"void Start () { MyClient = new Client("http://95.232.201.42:35352"); //Custom Port MyClient.Message += SocketMessage; MyClient.Opened += SocketOpened; MyClient.SocketConnectionClosed += SocketConnectionClosed; MyClient.Error += SocketError;

    MyClient.Connect();
}

"

The socket server doesn't detect the connection, and I know it works because I've had it work with other utilities. Either i'm not giving the correct URi/URL or this is too outdated.

CSEliot avatar Mar 09 '15 05:03 CSEliot

What version of Socket.io are you using?

squaretone avatar Apr 14 '15 13:04 squaretone

It's old, something like 0.9 in my experience with this module.

On 14 April 2015 at 16:59, Eric Lawrence [email protected] wrote:

What version of Socket.io are you using?

— Reply to this email directly or view it on GitHub https://github.com/NetEase/UnitySocketIO/issues/35#issuecomment-92861684 .

corsa1r avatar Apr 14 '15 14:04 corsa1r

I'm having the same issue with the latest version of socket io, except I'm getting an error callback with message: Error initializing handshake with ws://localhost:3000

Any ideas? @squaretone

jamesw6811 avatar Jan 24 '16 18:01 jamesw6811

If you connect [email protected] from a Webclient wich works using socket.io<0.9 and try to upgrade to socket.io>0.9, you response like:

error: "Transport unknown"

And the application server, pomelo, doesn't knows about this request. If you upgrade the client version to the same of the server (in my case [email protected], client and server side) it completes the handshake.

cc @squaretone @jamesw6811

frabaglia avatar Jun 20 '17 23:06 frabaglia