express.io
express.io copied to clipboard
socket.io 1.0.3 is out
Any plans to support v1 of socket.io?
The problem now is that express.io is not compatible with the latest release of socket.io any more...
Hows the community support of the new socket.io?
I know its a major overhaul.
Awesome, glad this is finally out.
The biggest thing on our roadmap is going to be upgrading to express 4.x and socket.io 1.x.
:+1: Looking forward to this!
hi @techpines love what you do, any chance you can make an estimate when express4 / socket.io 1 are supported? any chance i could help with it? i also face the challange of setting up one app after the next
I also have the same problem.
I need some feaetures which are in the later releases of express and are not supported in the modules included currently.
I am also happy to help out with development.
I will attempt to update the versions and figure out how to run the tests. etc.
I would like to not reinvent the wheel by doing all the integration again.
We as well would love to know the timetable for your roadmap to get Express 4 and socket.io 1+ into ExpressIO. If there is anything we can do to help, like above, let us know.
Thanks, we're currently working on it, but I don't have an eta.
@techpines we've been using express.io in production for a while, and I would love to use the features of socket.io 1.x in production. do you guys have an eta for this?
@techpines, do you guys have any update on the eta? What type of issues are you guys running into?
I don't have an eta, we're trying to get express updated to 4.x first, but we are trying to work out a session issue.
I am very interested in this upgrade aswell!
I'm also waiting the upgrade ! Need to work with the new express.Router() !
I am also very interested, is there an estimate when Express 4 and Socket.io 1+ will be supported?
@sibartlett has a fork that we're using for our project https://github.com/sibartlett/express.oi
It would be nice to just have it upstream though...
Yay for forks! I can't believe that isn't figured out yet... express.oi doesn't happen to support sessions/express 4?
@taytayevanson yes, express.oi supports sessions and express 4.
I've changed the API so that websocket requests use a similar API to regular express requests (req, res).
For instance, instead of calling req.io.respond()
, you call res.json()
.
I have yet to update the documentation and tests though.
@sibartlett @hhaidar this is a great fork, thanks for upgrading the deps to Express 4 and Socket.io 1.3. Is there any roadmap for documenting your API changes? For example, I'm not sure how I'd broadcast events as only app.io seems to respond to emit() and nothing else. Some small code examples from your project would be really helpful!
@lushc I'm planning to remove all the existing examples, and replace with one simple example which shows the API. I've started on this, so hope to have the repository updated in the next couple of days.
You can use the socket.io socket directly, like so:
if (req.isSocket) {
req.socket.emit('hey', { text: 'Hello world' });
}
I'm also open to suggestions/ideas in regards to improving the API.
@sibartlett ah, and I was so close, thank you! I see express.oi is used in Let's Chat so I'll use that for future reference (which, incidentally, is also showing me how much better I should be architecturing my node projects).
@lushc I just published a new version of express.oi, and updated the README with example usage.
@sibartlett Brilliant, I've been working with the lib today and the example usage was very helpful. This could have been a major blocker for the project I'm working on, really grateful for you updating the docs so quickly.