Database sessions are also discussed in the main book section on sessions<http://web2py.com/books/default/chapter/29/04/the-core#session>, along with the cookie based session option (which can also be helpful for high availability).
Anthony On Thursday, October 3, 2013 4:55:24 AM UTC-4, Niphlod wrote: > > why doesn't anyone search the book before asking ??? :-P > > > http://web2py.com/books/default/chapter/29/13/deployment-recipes#Efficiency-and-scalability > > Il giorno mercoledì 2 ottobre 2013 15:45:21 UTC+2, damona ha scritto: >> >> Any thoughts on this for clustering and High Availability? >> >> Could a feature be added to web2py to store session information in the >> DB, so using sticky session is optional, or if a server goes down it can >> get the session information. >> >> e.g. >> >> Proxy with stick session too server A and B >> Web2py on servers A and B store session information in DB when it changes. >> Server B goes down, everyone ones requests goes to server A >> Server A is sent a session which it does no know about, it looks it up in >> the DB. >> Users never knows that server B went down. >> >> You could also as part of the session record a modification date, and if >> it does not match what web2py has recorded locally it then looks it in the >> DB as well. This would also allow you not to have sticky sessions. >> >> Cheers. >> PS I would have thought GAE would have to store session information in >> Datastore/MySQL already? >> > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
