Multiple connections can be made that keep state in a non-transactional/distributed location. This can lead to things where one worker gets a request, saves state in itself temporarily, and then another worker gets a new request dependent on the state in the original worker.
req1 -> A -> save state to memory/tmp location req2 -> B -> does not have req1's state On Sunday, June 17, 2012 4:44:47 PM UTC-5, ryandesign wrote: > > In what way? > > > On Jun 17, 2012, at 03:08, Fadrizul H wrote: > > > Yeah, clustering is awesome. But if you start using sockets or the > module socket.io. then all hell breaks loose. >.< > > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
