point of clarification on what my app is doing 4 async calls being made, only one of which is trying to update the session but Beaker is loading and saving the session on every request due to the session access in setup_i8n() so depending on the timing, on of the other 3 can interfere with the one actually doing the work.
so a few solutions come to mind 1) structure my app, so that that session updates happen in isolation from other async requests 2) disable setup_i8n() 3) disable the session.persist() call built into the beaker middleware, and call session.persist() myself when I know I want to thoughts? On Dec 23, 10:57 pm, qwcode <[email protected]> wrote: > Hello: > > the core tg2 controller, "TGController" calls setup_i18n() on every > request > setup_i18n() peforms a request to the session. > > Beaker (the tg2 session library) detects this session access, and > decides to save the session on every request (irregardless of whether > my app uses the session) > > Is this an accurate account of what happens? > > This is a problem for me, because session data is being overwritten by > session saves in other async/ajax requests. > > What should I do? besides comment out the call to setup_i18n(), which > I think I don't need. > > any help appreciated. -- 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.
