Session loaded in the server

[awwx]

I was surprised to see Session loaded on the server

meteor/app/lib/packages.js

Line 134 in 5bdb378

api.use(['deps', 'session', 'livedata', 'mongo-livedata', 'spark',

meteor/packages/session/package.js

Line 12 in 5bdb378

where = where || ['client', 'server'];

as the docs say

Session provides a global object on the client

and naturally the in-memory implementation won't do much good with multiple server instances.

I expect someone is going to get bitten by this eventually; they'll overlook the note that Session is for the client and write some cool reactive server-side Session code that will work fine during development and then break when deployed.

[avital]

I've seen people be confused about this before.

On Mon, Feb 25, 2013 at 2:01 PM, Andrew Wilcox notifications@github.comwrote:

I was surprised to see Session loaded on the server

meteor/app/lib/packages.js

Line 134 in 5bdb378

api.use(['deps', 'session', 'livedata', 'mongo-livedata', 'spark',

meteor/packages/session/package.js

Line 12 in 5bdb378

where = where || ['client', 'server'];

as the docs say

Session provides a global object on the client

and naturally the in-memory implementation won't do much good with
multiple server instances.

I expect someone is going to get bitten by this eventually; they'll
overlook the note that Session is for the client and write some cool
reactive server-side Session code that will work fine during development
and then break when deployed.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/751.

[timhaines]

I've been confused about this before. I'd been working with Meteor for a couple of months before I realized sessions were only client side and only lasted until you refreshed the page. Most of what I'd been working on didn't make much use of session (my partner's code did), but I wish I'd been prodded to read about them earlier.

[glasser]

Fixed on devel.