Session modification sensing
|Reported by:||Owned by:||Adrian Holovaty|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
Currently, the session is saved only when the session object itself is touched (keys are added, deleted, values modified). This is even described as a "gotcha" in the official documentation. How about changing this to sense changes anywhere deep in the session objects?
My scenario is as follows:
request.sessionxxx? = 
The sensing mechanism could compare the pickled values (this would require storing the original session's pickle somewhere at the start of a request) or hash values to conserve a bit of memory (I guess would be all right for most purposes but not bulletproof).
If the proposal is accepted, I could write a patch.