You are right. That does use memcache. I forgot about it. I will run some tests and let you know.
Massimo On Mar 15, 11:27 am, Ted G <[email protected]> wrote: > I guess I have misinterpreted this code from my db.py which was part > of the web2py distro that I uncommented. The comments within the code > stated the sessions would be stored in memcache. > > try: > from gluon.contrib.gql import * # if running on Google App Engine > except: > db = SQLDB('sqlite://storage.db') # if not, use SQLite or other > DB > else: > db = GQLDB() # connect to Google BigTable > #session.connect(request, response, db=db) # and store sessions > there > # or use the following lines to store sessions in Memcache > from gluon.contrib.memdb import MEMDB > from google.appengine.api.memcache import Client > session.connect(request, response, db=MEMDB(Client())) > > from gluon.contrib.gae_memcache import MemcacheClient > cache.ram=cache.disk=MemcacheClient(request) > > On Mar 11, 11:34 am, mdipierro <[email protected]> wrote: > > > How are you doing this? web2py does not provide an API to store > > sessions in memcache. If you have implemented it perhaps we should > > include it in web2py so I can help debug it if there is a problem. > > > On Mar 11, 12:04 pm, Ted G <[email protected]> wrote: > > > > I'm seeing this behaviour as well (on GAE live but not SDK). In my > > > case sessions are in memcache not db. Can't pinpoint when it started > > > but noticed it earlier this week. Haven't updated web2py in quite some > > > time (I've been running 1.65.11). > > > > On Mar 10, 4:47 pm, Richard <[email protected]> wrote: > > > > > I forgot to mention something crucial - this is for web2py on GAE. > > > > > Apparently another user is also experiencing sessions problems on > > > > GAE:http://groups.google.com/group/web2py/browse_thread/thread/a5699d4788... > > > > > On Mar 11, 4:00 am, mdipierro <[email protected]> wrote: > > > > > > I cannot find the problem. I could use some help debugging this. Can > > > > > people reproduce it? > > > > > > On Mar 10, 6:28 am, Richard <[email protected]> wrote: > > > > > > > I find my auth sessions are expiring after about 5 minutes. I have > > > > > > tried setting "auth.settings.expiration = 999999999" but it seems to > > > > > > make no difference. > > > > > > > I recently upgraded to 1.76.3 and don't remember experiencing this > > > > > > before - is there a new way to set session expiration length? > > > > > > > Richard -- You received this message because you are subscribed to the Google Groups "web2py-users" 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/web2py?hl=en.
