Client doesn't work with Node.js socket.io server about go-socket.io HOT 24 CLOSED

Which version of socket.io at node.js server? I only tested with socket.io 0.9.

from go-socket.io.

I tried it with the latest, 1.0.5.

I'll give it a try with 0.9, thanks :-)

David Dawson
CEO, Principal Consultant
Simplicity Itself Limited
Tel +447866011256
Skype: davidadawson
[email protected]
http://www.simplicityitself.com

from go-socket.io.

I've tried with 0.9 server and that does with with this lib so far. I'm happy to do that as it's a new project and go compatibility is one of the priorities.

Looking good, but might be worth a note that 1.0.5 compatibility isn't there yet perhaps?

from go-socket.io.

No. I'm working on 1.0 now. socket.io changed a lot after I finished my code. I need to redesign all from bottom :(

from go-socket.io.

@googollee would you be open to externalizing your objectives and needs for 1.0 compatibility? I'm in need of a full 1.0 compatible client, else will be switching to node for my current need to prevent being incompatible with new clients (and also with the lack of long polling support).

Happy to help - just needing direction.

from go-socket.io.

@MattNewberry socket.io 1.0 separated connection layer to engine.io. I'm working on porting engine.io these days, with long polling support. I think I will finish it this week. Then I will move on to port socket.io 1.0. But I can't say the schedule. I'm doing it on my free time.

from go-socket.io.

If you're open to publishing your work to a new branch and defining what needs to be done, I'm sure multiple people would be open toward contributing, including myself.

from go-socket.io.

Yes I will publish it. I just, want to make it work first then publish.

from go-socket.io.

Just published go-engine.io and will move on to implement socket.io 1.0 based on it.

from go-socket.io.

💯

from go-socket.io.

Very impressive!

from go-socket.io.

hi, everyone, I just pushed branch 1.0 which support latest socket.io implement. Welcome to try and feedback.

It support long polling and room. I try to add more unit test now and make it stable.

Please tell me your feeling.

from go-socket.io.

Awesome news! Thank you for all your work!

from go-socket.io.

Oh, I don't implement client now. The branch is only server part.

from go-socket.io.

The 1.0 branch works fine with me (with socket.io-1.0.6.js, downloaded from http://socket.io/download/). Room support and long polling both working from what I can tell.

Do you anticipate moving the 1.0 branch to master soon? I couldnt figure out a good way to get the code using go get (no branch support on github from what I could tell). Maybe move 0.9 support to a separate repo?

Anyway - great project, thank you!

from go-socket.io.

@jgoodall Yes. I still want to change the implement of room adaptor, to make it more easy to add another adaptor, like redis. After that, I will make it master branch.

I'm glad to see you happy with my project. :)

I'm not sure how to deal with 0.9 support. Make a new repo or a new branch? Seems if want to use go get easily, new repo is more comfortable way.

from go-socket.io.

@jgoodall I just move 1.0 branch to master, and make a 0.9.x branch for old code.

from go-socket.io.

great, go get works as expected.

from go-socket.io.

Thanks for all your work! Any ETA on the client implementation?

from go-socket.io.

for using go get with 0.9 vs 1.0 - I hadnt realized this, but maybe you can use -tags

from go-socket.io.

@MattNewberry I will do the client, but not sure the finish time. I'm working on CoreOS/etcd now. I will do it when I finish the CoreOS issue.

I will keep this issue open till the client finished. Do you need the client urgently?

from go-socket.io.

@jgoodall Yes there is a 0.9.x tag for 0.9 implement.

from go-socket.io.

That's great - I've tinkered with CoreOS before, it's a great project I hope to use in the future. It's not an urgent matter, but will be useful once completed for my test harness.

from go-socket.io.

Hi everyone, could you try latest version? Please update go-engine.io which is the base of go-socket.io. And it fixed a lot of bugs like no disconnect event.

And if meet any issue, please open a new issue.

from go-socket.io.