share the session and cache safely amongst all instances with a single entry point.
This may require using either a DB or shared file system or a memcached and avoid the memory http://turbogears.org/2.1/docs/main/Session.html Normaly this is all in the settings of beaker. 2011/10/19 Rotem Tamir <[email protected]>: > I have a TG2.1 app using sessions ( like > session.get('game_object',None) ) > > I am going into production soon and I'll have multiple instances > behind an nginx server. > > If I understand correctly, then session data is kept per-instance, > this means that if in the round-robin between instances, somtimes > instance A will respond to my user and another time instance B, this > is a big problem since the user's data needs to persist.. > > How do you guys solve this kind of problem? > > > Thanks in advance, > Rotem > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" 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/turbogears?hl=en. > > -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
