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
[1.0.4] cocos2dx socketIO - Migrating from 0.9 issue #1628
Comments
Here: https://github.com/Automattic/engine.io-protocol#urls Replacement of |
@hden |
Try GET response 200
The b64 flag specifies base64 encoding To perform further action, try GET response 200
|
I tried like below request
response
and transport websocket using sid(session key) request
response
In 0.9 version of socket.io, websocket url was
In 1.0.4 version, where I connect to? |
Please do a transport upgrade Corresponding JavaScript code |
But there is no way for legacy clients, say... deployed mobile clients to connect with websockets first to a 1.0 socket.io server? |
Nope according to the spec. Legacy clients does not have corresponding parser in the first place. |
thanks @hden
and what means 2:40 ? |
thanks i'll see them too i'm modifying cocos2d-x source socketIO.cpp i changed this line
to
like this. and this block to
for updated version. this block parses so then handshake is done. next call opensocket function In last version of socket.io url was help to change this line I tried but it returns error according to engine.io README document it may needs to a upgrade transport how to upgrade transport? thanks |
upgrade packet. corresponding code |
is there any update on this? is it solved yet? really need this for my game :( |
I'm just starting to look at this, and having the same issues. Some of the problems addressed above are just json parsing problems. Maybe Cocos2d-x would benefit from am integrated json parser. |
there is a library in %cocos2d-x-root%/external/json. maybe you could try to look at that |
I'm writting a Unity-Socket.IO plugin so I've been working with the message parsing. What I've found is that the first digit matches an Engine.IO packet type id. (https://github.com/automattic/engine.io-protocol#packet) The second digit it's the Socket.IO packet ID. Using this rule, a packet "40" actually means Edit: |
is there any solution for connection to Socket.io version 1 from cocos2d-x? |
FYI there has been discussion of this subject on the Cocos2d-x forum, including a response from Chris Hannon, the author of the SIOClient class: http://discuss.cocos2d-x.org/t/sioclient-bug-found-in-emit-function/15526 |
Closed due to inactivity, please reopen if needed. |
handshaking issue
I can't find handshake url
0.9 under - http://uri/socket.io/1
1.0.4 - http://uri/socket.io/?EIO=2&transport=polling <----- ??
I just found with packet sniffer
it returns sid and pinginterval timeout with http response code 200
but return value has binary data beginning of value <--- just right?
i don't know exactly what this value is correct.
and then I want connect to websocket but can't find any documents for version 1.0.4
where i connect to?
The text was updated successfully, but these errors were encountered: