这是一个很晚的回复,但我希望它对您有用。我只花了大约四个小时试图解决这个问题。
您将遇到的第一个问题是koa-session 不使用真正的会话存储。它将所有信息嵌入 cookie 本身,然后将其解析到客户端和从客户端解析。虽然这很方便,但在尝试合并 Socket.IO 时对您不利,因为 Socket.IO 无法访问 koa-session。
您需要迁移到 koa-generic-session 并使用会话存储来跟踪您的会话。在我看来,这是一个更好的举措。我目前正在为我的会话存储使用koa-redis。
为了在Socket.IO 中访问您的会话,您需要设置一个全局存储。这是我的全球商店的样子。
// store.js
var RedisStore = require('koa-redis'),
store = undefined; // global
module.exports = function(app, settings) {
// Where (app) is Koa and (settings) is arbitrary information
return (function(app, settings) {
store = store || new RedisStore();
return store;
})(app, settings);
}
之后,初始设置就很容易了。
// app.js
... arbitrary code here ...
var session = require('koa-generic-session');
app.keys = [config.secret];
app.use(session({
store: require('./store')(app, settings)
}));
... arbitrary code here ...
现在您有了一个全局会话存储,您可以在Socket.IO 中访问它。请记住,您需要安装 cookie 和 co 模块。
// io.js
var cookie = require('cookie'),
co = require('co'),
store = require('./store')(null, settings); // We don't require the Koa app
io.use(function(socket, next){
// Now you will need to set up the authorization middleware. In order to
// authenticate, you will need the SID from the cookie generated by
// koa-generic-session. The property name is by default 'koa.sid'.
var sid = cookie.parse(socket.handshake.headers.cookie)['koa.sid'];
// We need co to handle generators for us or everything will blow up
// when you try to access data stores designed for Koa.
co(function*(){
// 'koa:sess:' is the default prefix for generic sessions.
var session = yield store.get('koa:sess:' + sid);
// At this point you can do any validation you'd like. If all is well,
// authorize the connection. Feel free to add any additional properties
// to the handshake from the session if you please.
if (session) next(null, true) // authenticated
else throw new Error('Authentication error.');
});
});
io.on('connection', function(socket){
// Access handshake here.
});
我已经调整了Socket.IO v1 的代码。我希望这会有所帮助。