What is the best way to do that (and keep it compatible for not GAE deployments)?
On Mar 10, 11:40 am, mdipierro <[email protected]> wrote: > session.forget() does not remove the session record on GAE because it > is created in order to get a session_id. It just prevents the write of > the data in the session record. It cannot delete the session > automatically because the session bay have been created by another > request and contain data used by another request. You must delete it > yourself it you know it is safe. > > On Mar 10, 10:03 am, chris p <[email protected]> wrote: > > > > > I have a small app running on the google app engine, with some > > controllers called from crons. Each time this happens, a session > > object gets stored for the call, which in my app is unnecessary. I > > have added a call to session.forget() (actually I just uncommented the > > one already in the default model/db.py) but the sessions records are > > still getting created. I can remove the session.connect() call too, > > but isn't session.forget() supposed to remove the session data? -- 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.
