[Zope] [Warning] Potential serious Session/TemporaryStorage problem

[Dieter Maurer]

Recently, strange session related "Conflict Errors" have been reported.

The strange thing about these conflicts is that the timestamp
when the object was read from the ZODB is *AFTER* the timestamp
the object has at commit time. Apparently, the object state
jumped backward in time. When the object is modified, this
results in a "ConflictError". However, when the object is only
read, then old data is used -- probably without anyone noticing
this.

This might be a reason for the many inconsistencies
Zope's Session implementation is plagued with.

Here is the respective collector entry:
http://collector.zope.org/Zope/1488


I will try to localize the place where this jumping backward in
time happens.

-- 
Dieter