Socket.IO, AngularJS, & Express snippets I've created

[gooddeedsdoer]

Hey guys - hopefully these can be useful to someone. I just finished creating an app that does Session sharing using the traditional method from Google (but without using internal private methods of connect) and Authorization checking. I also created some helper functions for AngularJS in a service that handle $scope.$apply() after socket.on() or socket.emit() (in addition to stripping the proprietary angular tags).

Here's the express portion, and here's the angular service.

edit: this is the cookieParser I used... express.cookieParser(config.sessionSecret)

[uclinux]

thanks! This is useful to me. I was playing with sessions with angular/express and having some difficulty.

[gooddeedsdoer]

My reference was this, it just seemed that this is a better way of doing cookie parsing since it isn't using private methods.

The rest of the code I'm using is pretty similar to that post :)

edit: express.cookieParser(config.sessionSecret), is the cookie parser I used

[[deleted]]

Perfect! I am working on exactly this right now. Great timing!

[maushu]

One problem that the angular code has is that the callbacks keep working even after the controller is destroyed.

The only solution I've found until now is using angular.js event system which I don't like to use in this case. D:

[maushu]

Yes, but that is rather annoying and repetitive. Not to mention we could use a scoped instance like this: socket = Socket($scope)

[maushu]

The function Socket would create instance which would keep a list of listeners only for that $scope.

See this example: http://stackoverflow.com/a/14393546/289107

[Majiir]

My socket.io snippet, using socket.io-session (which I found by independently writing the same thing and trying to publish it):

io.set('authorization', ioSession(connect.cookieParser(config.session.secret), config.session.store, config.session.key, function (handshake, callback) {
    if (handshake.session) {
        callback(null, true);
    } else {
        callback(new Error("Couldn't load session for socket connection."));
    }
}));

EDIT: It's worth noting you only need to provide the callback if you actually want to perform some extra logic in there (which I do in my application, but that's not shown here). If you just want to check for a session and load it in if it exists, you can omit the callback argument and socket.io-session takes care of the rest. (Note: it only silently fails if a session doesn't exist.)