npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

socket.io.session

v1.0.13

Published

get/set the same session content with the middleware 'express-session' from the socket object generated from socket.io

Downloads

13

Readme

socket.io.session

get/set the same session content with the middleware 'express-session'.


##Install

	npm install socket.io.session

##Config

    var session         = require('express-session');
    var RedisStore      = require('connect-redis')(session);
    var redis           = require('redis');
    var socketIOSession = require("socket.io.session");
    
    var redisClient     = redis.createClient();
    
    var sessionStore = new RedisStore({
      "client": redisClient,
      "host": "127.0.0.1",
      "port": 6379
    });
    
    
    //if you dont wanna use redis as session store
    //you can just use "session.MemoryStore"
    //memoryStore is binded with express-session as a fallback storage
    
    var sessionSettings = {
      "store": sessionStore, // or session.MemoryStore
      "secret": "your secret",
      "cookie": { "path": '/', "httpOnly": true, "secure": false,  "maxAge": null }
    };
    
    //used for http session
    app.use(session(sessionSettings));
    
    var server = require('http').Server(app);
    var io = require('socket.io')(server);
    
    
    //"sessionSettings" same config as http-session used 
    var socketSession = socketIOSession(sessionSettings); 
    
    //so it's better to make them global avaliable
    global.io            = io
    global.socketSession = socketSession
    
    //parse the "/" namespace
    io.use(socketSession.parser);
    
    // define a new namespace
    var chat = io
      .of("/chat")
      .on("connection",function(socket){
        console.log(socket.session);//same as http request.session
        
        //change session content
        socket.session.login = true
        
        //save the changed session ,at the same time http req.session changed too
        socketSession.save(socket)
        
        //or you can destory session that is attached on the specific  socket 
        socketSession.destroy(socket)
        
        //same as "destroy"
        socketSession.clear(socket);
        
      });
    
    //parse "/chat" namespace, must use parser for each namespace
    chat.use(socketSession.parser);
    
    
    app.use('/', someRoutes);
    server.listen(8080, function() {
      console.log('Express server listening on port ' +   server. address().port);
      console.log('http://localhost:' + server.address().port);
    });

Note:

  1. it's based on express-session
  2. socket.session == req.session, change one of them, the other one change too
  3. Email is the best way to let me know about the tool's issue([email protected])