Well, I was also shamed into creating a new implementation of the
sessioning stuff that might work better under higher load.

The people that are now having problems should try to replace the file
in their Zope software home named
"lib/python/Products/Transience/Transience.py" with this one:

http://cvs.zope.org/*checkout*/Zope/lib/python/Products/Transience/Transience.py?rev=1.32.12.2.2.1

(be sure to make a backup of the original file first)

After putting the new file in place, restart Zope and see what happens. 
This stuff was just checked in, so there's sure to be some edge case
bugs, but all the unit tests pass and the UI still works.  Please report
results back here, if possible.

Thanks!

- C


On Sun, 2004-02-29 at 01:11, Santi Camps wrote:
> > When we started using Zope sessions, we experienced a set
> > of session problems. I started fixing them, but it turned out
> > that the implementation was very ambitious, too ambitious to
> > get it safe. I, therefore, switched plans and implemented
> > an alternative "Transience" module -- much simpler and less ambitious.
> > We use it since then in a medium load production
> > environment and did not see any more problems.
> > 
> > I asked my boss whether I can release this implementation
> > as "Open Source". He said "sure".
> > 
> > I still have to hash out a few organisational questions but
> > I expect the module will be available within 2 weeks.
> 
> Oh, these are really good news !!  
> 
> Please, announce it very high :-)
> 
> Thanks a lot


_______________________________________________
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope-announce
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to