Closed pnitsch closed 13 years ago
what session store are you using? if it's the memory store, then use something persistant like connect-redis etc
Worked like a charm. Thanks for pointing out that lib.
relying on memory state is usually bad :p memory store is only good for testing really
I was unaware. Glad I posted the issue. :)
Might be more related to connect than cluster, but it's something to be aware of. I've been playing with a web app that uses connect sessions heavily. With two workers spawned the session id can occasionally change, most likely due to the request being handled by a different worker than the previous request.
Not sure if there's a workaround. I might try to write my own store and pass id's along with the request. Dunno.