Question

I’m just getting started with SocketStream. (v0.1.0) I created the file /app/server/auth.coffee with an exports.actions.login function. I’d like to access @session.setUserId in this file, but I’m have a hard time figuring out where @session lives and how to access it outside of /app/server/app.coffee

Here is my auth.coffee with comments where I’d like to access the session.

users = [
  username: 'craig'
  password: 'craig',
  username: 'joe'
  password: 'joe',
]

authenticate = (credentials, cb) ->
  user = _.detect users, (user) ->
    user.username == credentials.username and user.password == credentials.password
  authenticated = true if user?
  callback cb, authenticated

exports.actions = 
  login: (credentials, cb) ->
    authenticate credentials, (user) ->
      # here is where i'd like to set the userId like so:
      # @session.setUserId credentials.username
      callback cb user

Answer 1

Interesting you bring a question about sessions up at the moment as I’ve been re-writing a lot of this code over the last few days as part of SocketStream 0.2.

The good news is the @session variable will be back in 0.2 as I have found an efficient way to pass the session data through to the back end without having to use the ugly @getSession callback.

To answer your question specifically, the @session variable is simply another property which is injected into the export.actions object before the request is processed. Hence you cannot have an action called ‘session’ (though the name of this ‘magic variable’ will be configurable in the next release of 0.2).

The exports.authenticate = true setting does not apply in your case.

I’m interested to know how/why you’d like to use the @session object outside of your /app/server code.

I will be committing all the latest session code to the 0.2 preview branch on github in a few days time.

Hope that helps,

Owen