Since HTTP driven applications are stateless, sessions provide a way to store information about the user across requests. NodeSession ships with a variety of session back-ends available for use through a clean, unified API. Support for back-ends such as Memory, File and databases is included out of the box.

By default session middleware is turned off in app/config/middleware.js. Be sure to turn it on if your application needs session support.

The session configuration is stored in app/config/session.js. Be sure to review the well documented options available to you in this file. By default, Quorra is configured to use the memory session driver.

warning: Memory session driver is purposely not designed for a production environment. It will leak memory under most conditions, does not scale past a single process, and is meant for debugging and developing.

Reserved Keys

The Quorra framework uses the flash session key internally, so you should not add an item to the session by that name.

Session Usage

The session can be accessed via the HTTP request object's session property.

Storing An Item In The Session

req.session.put('key', 'value');

Push A Value Onto An Array Session Value

req.session.push('user.teams', 'developers');

Retrieving An Item From The Session

var value = req.session.get('key');

Retrieving An Item Or Returning A Default Value

var value = req.session.get('key', 'default');

Retrieving An Item And Forgetting It

var value = req.session.pull('key', 'default');

Retrieving All Data From The Session

var data = req.session.all();

Determining If An Item Exists In The Session

if (req.session.has('users'))

Removing An Item From The Session


Removing All Items From The Session


Regenerating The Session ID


Flash Data

Sometimes you may wish to store items in the session only for the next request. You may do so using the req.session .flash method:

req.session.flash('key', 'value');

Reflashing The Current Flash Data For Another Request


Reflashing Only A Subset Of Flash Data

req.session.keep('username', 'email');

Database Sessions

When using the database session driver, you may need to setup a table to contain the session items based on database. Below is a required schema for the table:

filed type index
id string unique
payload string
lastActivity integer

Session Drivers

The session "driver" defines where session data will be stored for each request. Quorra ships with several great drivers out of the box:

  • memory - sessions will be stored in memory(only for test and debug purpose).
  • file - sessions will be stored in files in a specified location.
  • database - sessions will be stored in a database.