I manually set the req.session.modified flag when I updated the value.
I've spent some time trying to think of an automatic way of determining
if the session was modified.
They key is save the state of the session at the beginning of the
request, and then compare it at the end to see if changes w
On 11/14/05, Kevin <[EMAIL PROTECTED]> wrote:
> I want to second the idea of a config variable for saving the session
> on each request.
As of trunk revision 1303, there's a SESSION_SAVE_EVERY_REQUEST
setting. It's set to False by default. I've updated the docs:
http://www.djangoproject.com/docu
I want to second the idea of a config variable for saving the session
on each request. I got stuck on a bug where my sessions never seemed
to be saved. I'm creating an shopping engine in django, and need to
store a lot of data in a session, and so I wanted to partition the data
a bit for better
Adrian Holovaty wrote:
I see two solutions:
- generate new session key when processing request immediately if there
is no cookie
I don't see this as a viable solution, because that would require a
database hit for every request that doesn't have a session -- which
isn't good for performa
On 11/11/05, Maniac <[EMAIL PROTECTED]> wrote:
> 1. Session key is generated on save, not on creation.
> [...]
> So when new user (without a session cookie) makes a request I'm trying
> to create a session and create a new Basket referencing to this new
> session. Here's the trap: until the reques
Hello!
I recently discovered some annoyances in sessions middleware which I'd
like to fix. But first I prefer to here from you if this is desirable.
1. Session key is generated on save, not on creation.
This means that Django may expose the working and usable session to the
user which nonet
