On Dec 20, 2005, at 12:36 AM, Dennis Allison wrote:
The interaction between sessions, conflicts, and persistence is a bit
confusing. I am still trying to understand the code in depth.
One thing is for sure, request.SESSION and/or request['SESSION']
must be
persistent for things to work.
Chris McDonough identified a persistence problem with the routine(s) that
manage sessions variables. (Thanks Chris) I have put the correction in
place which resolved some (but not all) of the problems.
There are still problems which are apparently due conflicts in accessing
the session
The interaction between sessions, conflicts, and persistence is a bit
confusing. I am still trying to understand the code in depth.
One thing is for sure, request.SESSION and/or request['SESSION'] must be
persistent for things to work. Mutable objects in the session variable
set
[Using zope-dev@ instead of [EMAIL PROTECTED]
Dennis Allison wrote:
A more session-friendly conflict resolution might use:
1. if any of the states are invalid (that is, has a key '_invalid')
return the invalid state.
2. if any any of the states attributes
Code would be good.
Note that changing the transientobject conflict resolution algorithm
won't get rid of all write conflict errors, because the BTree-based
indexes in the transient object container will still conflict during
a bucket split and other situations that I can't exactly recall
[Chris McDonough]
Note that changing the transientobject conflict resolution algorithm
won't get rid of all write conflict errors, because the BTree-based
indexes in the transient object container will still conflict during a
bucket split and other situations that I can't exactly recall
Zope 2.8.4, ZODB 3.4.2
Chris,
I'm pretty sure that I mentioned having done that in one of my postings.
I have followed your recommendations, but the problem remains. (um...
persists grin)
The systems are running a Zope/ZEO combination with a store configuration
of:
#
zodb_db temporary
Trimmed zodb-dev off the cc list.
On Dec 15, 2005, at 2:24 PM, Dennis Allison wrote:
The systems are running a Zope/ZEO combination with a store
configuration
of:
#
zodb_db temporary
# Temporary storage database (for sessions)
temporarystorage
name temporary storage for
On 12/16/05, Dennis Allison [EMAIL PROTECTED] wrote:
MAYBE CONFLICTS AND THEIR RESOLUTION ARE NOT THE ROOT CAUSE OF THE SESSION
VARIABLE PROBLEM. The observed problem is that session variables suddenly
disappear.
Perhaps your app is tripping over some bug in conflict handling. But
I'd say it
