Thanks for the question Jonathon, I actually did do some debugging similar to what you recommended.
The answer to my confusion is: I manually set beaker.session.cookie_expires and session.timeout and got some very wacky behavior (e.g. inconsistent across browsers/ platforms). My caveat to people is to stick with the defaults unless you *really* understand what's going on. On Nov 23, 9:04 am, Jonathan Vanasco <[email protected]> wrote: > silly question -- is there anything in those ajax calls that clears > the session, or updates the session with a null value ? > > try adding a few debug/print statements in your ajax calls to figure > out exactly where the clearing occurs > > On Nov 19, 8:50 pm, tobin <[email protected]> wrote: > > > So I've run into some odd behavior and am wondering if anyone has > > experienced this or has a solution: > > > I have a user-based Pylons website, requiring login/password and it > > stores a userid in the Pylons session. And it's worked fine for me > > until recently when: > > > I started populating data on the page with numerous Ajax calls > > (tens?). This has caused my session obj to disappear on proceeding > > pages - when I looking for my session['userid'] that was previously > > set, it's gone! > > > If i disable my ajax calls, all goes back to normal and works. > > > Ideas as to why this happens? -- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
