Hi Steve,
I have now implemented this option in the trunk,
http://svn.w4py.org/Webware/trunk in r8156.
You need to set AlwaysSaveSessions = False in
Application.config to activate it.
Let me know how it works as I want to release 1.1rc1 and then 1.1 as
soon as possible.
-- Christoph
Hi Steve,
thanks for the detailed write-up; I see the problem. The current session
handling is really not ideal when you're using AJAX (which is no wonder
since Webware has been designed before anybody even thought about that).
IMHO the most simple solution would be to keep a dirty flag (set
On Thu, Mar 3, 2011 at 9:28 AM, Christoph Zwerschke c...@online.de wrote:
IMHO the most simple solution would be to keep a dirty flag (set
whenever __setitem__ or __delitem__ is called for the session) and then
save the session only when the dirty flag has been set. This will also
be good for
Btw, which kind of session store are you using? The default DynamicStore
is based on the MemoryStore, and here requests share the same session
object. So the scenario you described should actually not cause a
problem for this kind of session store.
-- Christoph
On Thu, Mar 3, 2011 at 2:23 PM, Christoph Zwerschke c...@online.de wrote:
Btw, which kind of session store are you using? The default DynamicStore
is based on the MemoryStore, and here requests share the same session
object. So the scenario you described should actually not cause a
problem
Am 03.03.2011 21:38 schrieb Steve Schwarz:
We use multiple appservers without session affinity so we use
MemcacheSession to share sessions across appservers
Ok, that explains why you've run into that issue. The session objects
are not shared between threads in this case.
So the simplest
Hi,
We ran across an interesting problem with sessions being automatically saved
by Transaction.py. We had a situation where two AJAX requests were issued
and one of the requests updates the session and it started and completed
within the lifetime of another request. In that scenario the
