express.io icon indicating copy to clipboard operation
express.io copied to clipboard

socket.io 1.0.3 is out

Open jhfoo opened this issue 10 years ago • 22 comments

Any plans to support v1 of socket.io?

jhfoo avatar Jun 01 '14 22:06 jhfoo

The problem now is that express.io is not compatible with the latest release of socket.io any more...

jhfoo avatar Jun 02 '14 06:06 jhfoo

Hows the community support of the new socket.io?

I know its a major overhaul.

nullivex avatar Jun 02 '14 15:06 nullivex

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.

techpines avatar Jun 02 '14 15:06 techpines

:+1: Looking forward to this!

bpartridge83 avatar Jun 04 '14 01:06 bpartridge83

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

soliton4 avatar Jun 11 '14 11:06 soliton4

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.

abufilba avatar Jul 01 '14 09:07 abufilba

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.

tzaitsev avatar Jul 01 '14 20:07 tzaitsev

Thanks, we're currently working on it, but I don't have an eta.

techpines avatar Jul 01 '14 20:07 techpines

@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?

rohit8 avatar Jul 30 '14 17:07 rohit8

@techpines, do you guys have any update on the eta? What type of issues are you guys running into?

KamalAman avatar Jul 30 '14 21:07 KamalAman

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.

techpines avatar Jul 30 '14 21:07 techpines

I am very interested in this upgrade aswell!

janseo avatar Aug 18 '14 08:08 janseo

I'm also waiting the upgrade ! Need to work with the new express.Router() !

konsserto avatar Aug 20 '14 13:08 konsserto

I am also very interested, is there an estimate when Express 4 and Socket.io 1+ will be supported?

optimalisatie avatar Oct 05 '14 11:10 optimalisatie

@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...

hhaidar avatar Feb 14 '15 16:02 hhaidar

Yay for forks! I can't believe that isn't figured out yet... express.oi doesn't happen to support sessions/express 4?

taytayevanson avatar Feb 21 '15 04:02 taytayevanson

@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 avatar Feb 21 '15 06:02 sibartlett

@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 avatar Feb 26 '15 21:02 lushc

@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 avatar Feb 26 '15 22:02 sibartlett

@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 avatar Feb 26 '15 23:02 lushc

@lushc I just published a new version of express.oi, and updated the README with example usage.

sibartlett avatar Feb 27 '15 00:02 sibartlett

@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.

lushc avatar Feb 27 '15 19:02 lushc