-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Abandon? #1234
Comments
I don't think it's been abandoned, an update was posted not too long ago on the google group (https://groups.google.com/forum/?fromgroups#!topic/socket_io/NMqfaVMsV3o), but clearly there is a bit of confusion on what lack of updates to the codebase here on github. Almost seems like much of the work is not being pushed to this repo as development is happening. |
Definitely not abandoned, and I'll be pushing updates soon. Most of the On Thu, May 16, 2013 at 9:36 PM, cendrizzi [email protected] wrote:
Guillermo Rauch |
What's the status on this? Something coming up? |
@guille we need some information, its been a long time (again and again). Please share some insights. |
👍 so true, @guille I am really planning to use engine.io ...or should I wait till the new socket.io comes up? I mean, you have a (BIG) community, you should write those insights in the front page, not just as comment on an issue. (Even because last socket.io version was built on top of Node 0.6\8... now Node 0.10 came up with new stream APIs, I'm not using this environment but does it work as "expected"?) |
If you don't want to wait for Socket.IO 1.0 to happen or if you feel like this project is abandoned or you want to protect yourself and your project against future abandonware you might want to take a look at: Primus https://github.com/3rd-Eden/primus It which wraps around Engine.IO, SockJS, Pure WebSockets and more while maintaining a common unchanged interface between them all. It comes with a build reconnect support, automatic encoding/decoding of objects through customisable parsers and a plugin interface if you want to use use some higher level API's such as a build in event emitter, rooms or even namespaces. Or if that's to fancy for you can always just build upon Engine.IO and extend it your self. It's not that hard. |
@3rd-Eden yeah I was looking at it just earlier this morning. I'm not really sure I'll use it in what I am building right now, as it sounds too much "high level API", but I'll surely give it a chance :) It surely seems to be a very good project! |
Guys,
The project is being abandoned?
Makes 2 months since the last commit ..
The text was updated successfully, but these errors were encountered: