Use feathers-socketio? and rest&socket share session maybe?

[simonjoom]

I think we should to use express-session and no need anymore cookie-parser - > Since version 1.5.0, the cookie-parser middleware is no need

And add middleware fonctionnalities with socket-io

why not use share sessions between rest and socket to get things working all together?
why not use feathers-socketio instead socket?

see: http://stackoverflow.com/questions/25532692/how-to-share-sessions-with-socket-io-1-x-and-express-4-x

[daffl]

feathers-authentication does not use sessions. The Cookie parser is only for getting the JWT from a cookie which is usually only the case with server side rendering.

You can also already use your own Socket.io middleware as documented here.

[simonjoom]

Thks for replying, yes i saw it that it 's not using sessions.
Just can i ask why you decided that? better to use only cookie for server-side rendering?

In fact i was worry about cookies is not good.

but yes cookie-parser is not a real cookie, for me a cookie is stored in client-side.
I was worry about lost token when cookie is removed.

They should to not use this name 'cookie-parser' because it's just something in the request header.

[daffl]

Well cookie-parser just passes the cookie request header so the name isn't necessarily wrong. The cookie is just one way to provide the JWT though. You can easily disable cookies and manage the tokens yourself (the client does that for you already).