No commit message

Port mergeResults() tests

       splitlines() instead of split('\n').

docstring instead, as the new style suggests.

  - replaced old CVS expansion with a clean $Id$
  - set the svn:keywords property to "Id"

When you check-in files in the future and want $Id$ to be expanded,
make sure it reads "$Id$" in that file; then set svn:keywords to "Id".

ZODB, ZEO, Persistence and similar packages were not modified since they
are really maintained elsewhere. Right now, we use a copy of them in our
Zope/Zope3 trees. We should go back to the module sharing (using
svn:externals).

       in DA.py

connection can be holding on to an object with references to an object
that has been recently garbage collected.  When the object is unghosted in
the reference-holding thread, the storage cannot find the oid (because it's
out of storage due to gc).  We work around this by turning KeyErrors that
we believe are due to this scenario into ConflictErrors.

and closing a connection between each request.

New "Transience" implementation.  This implementation offers no new features,
but is is vastly simpler, which makes it easier to maintain.  The older version
used all sorts of (questionable) tricks to attempt to avoid conflicts and to
improve performance, such as using Python Queue-module queues to store action 
lists, using an index to quickly look up which "bucket" a transient object
was stored within and several other persistent objects which attempted to keep
pointers into the data.  The older version also had a lot of "voodoo" code in
it which papered over problems that was apparenly caused by its complexity.
This code is now removed/replaced and the implementation is fairly straight-
forward.

The newer version is probably much slower (due to the lack of an index, it
needs to scan all "current" buckets to attempt to find a value), but it 
operates reliably under high load. 

This implementation removes backwards compatibility support for transient
object containers persisted via the Zope 2.5.X implementation.  It is possible
to use it against instances created in Zope 2.6.X and better, and it
is possible after using it against a database created under one of these
flavors to move back to an "older" Zope in this range, although it is likely
that data in the TOC will be silently lost when this is done.

Added default configuration values to App.config

       Indexing errors are catched and logged. In addition the progress of the
       recataloging operation is logged. So one can see how much documents are
       already processed and how much documents are remaining.

       parameters from zope.conf as the low-level reStructuredText
       implementation.

       since the uninstall routine could also remove non-Zope files. Because
       this was to dangerous it has been removed completely.