[Zope] ZODB conflict error AFTER adding an 'Access Rules'

Dieter Maurer dieter at handshake.de
Thu Sep 25 13:10:26 EDT 2003


Jean Baltus wrote at 2003-9-25 16:22 +0200:
 > I don't have time to put on my swimsuit and dive into the ZODB today but
 > I will...
 > 
 > In the meantime, here is the exact copy of my access rule (in case you
 > notice something weird):
 > 
 > session = context.REQUEST.SESSION
 > path_info = context.REQUEST['PATH_INFO']
 > 
 > if not session.has_key('skin'):
 >   session.set('skin', 'bidon')
 > 
 > if path_info.find("/muse") >=0:
 >   session.set('skin', 'muse')
 > elif path_info.find("/res") >=0:
 >   session.set('skin', 'res')
 > 
 > if session['skin']== 'res':
 >   context.changeSkin('res')

Thus, you read and write "session".
Almost surely, this is the cause of your "ConflictError"s.

Session related conflicts are especially likely when
you use a frame based UI (as all frames in a frameset make
requests at the same time and are likely to access the
same session object).

Occational "ConflictError"s are harmless.
You can ignore them.


Dieter



More information about the Zope mailing list