New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Session loaded in the server #751

Closed
awwx opened this Issue Feb 25, 2013 · 3 comments

Comments

Projects
None yet
4 participants
@awwx
Contributor

awwx commented Feb 25, 2013

I was surprised to see Session loaded on the server

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

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

This comment has been minimized.

Contributor

avital commented Feb 25, 2013

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

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

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

This comment has been minimized.

Contributor

timhaines commented Feb 25, 2013

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

This comment has been minimized.

Member

glasser commented Mar 4, 2013

Fixed on devel.

@glasser glasser closed this Mar 4, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment