I think (in v 1.0) you can call session_store.save() -- I'm guessing that it will save immediately, but I'm not sure: http://docs.djangoproject.com/en/dev/topics/http/sessions/?from=olddocs#using-sessions-out-of-views
On Apr 16, 10:06 pm, leopay <leo...@gmail.com> wrote: > at first session["a"] is oldvalue, > request A set session["a"] to newvalue, before session.save to db,(as > in django, the session save action occur at end of the request), > meanwhile, request B arrive, but get session["a"] is still the > oldvalue, > how to handle this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
