SocketIO namespaces, paths and custom ACK

cocos2d-x
1

Maybe I’m doing things wrong but the current implementation von SocketIO is rather limited, isn’t it?

The features I’m missing are:

NOTE: It’s important not to mix namespaces and the path options together! path describes where the SocketIO server is placed/mounted (/socket.io/.. is the default “setup route” to establish new SockerIO connections, but with path=/foo this becomes /foo/socket.io/...). Whereas namespaces are used to multiplex different scopes over one connection.

I’ve tried to understand the current implementation but already the API is a bit, at least for me, confusing. So are those features implemented and I’m just using it wrong? If not, are they on the roadmap somewhere?

It would really be nice if we could get a feature complete implementation of SocketIO, as this is quite popular in the JS world and also a good foundation for HTML5 games.

Thanks a lot!
Michael

2

if you looking for another sockets try my socket implementation:

i am already use it at my multiplayer game

3

Thank you for this suggestion but I honestly don’t want to roll a custom network protocol. The server I’m writing should be compatible with both the native version of cocos2dx AND the html5 version. Also the SocketIO spec contains a lot of useful details (namespaces, rooms, boadcast, multiplexing, fallback transports etc.) that I don’t want to roll on my own.

So @slackmoehrle, would it be possible for you to ask the core team if full support for SockerIO is on the roadmap?

4

I don’t know this answer, but sure, I can ask.

1 Like
5

So I don’t see this on our roadmap, but if you create a GitHub issue, the correct folks will look at it.

6

@slackmoehrle Ok, thank you. I’ve created single issues for every missing feature:

7

Thank you, I will make sure those goto the right people.

8

Thank you! I’ve created a few more issues and here is a overview of all.

Hopefully they are not that hard to solve and we can have a more compatible SocketIO client in cocos2dx very soon :smile:

9

Did you write one issue for Namespace? I did not see it in your referenced link.

10

These are all SocketIO related issues reported by me