(https://bugs.launchpad.net/zodb/+bug/400775)

Also, stop producing legacy PersistentMapping state, while still
accepting it.

Simplified the file-storage configuration a bit.  Eliminated
duplication of defaults between the Python and ZConfig interfaces.

- Fixed vulnerabilities in the ZEO network protocol that allow:

CVE-2009-0668 Arbitrary Python code execution in ZODB ZEO storage servers
  CVE-2009-0669 Authentication bypass in ZODB ZEO storage servers

- Limit the number of object ids that can be allocated at once to
  avoid running out of memory.

- The "lawn" layout was being selected by default if the root of
  the blob directory happened to contain a hidden file or directory
  such as ".svn".  Now hidden files and directories are ignored
  when choosing the default layout.

- BlobStorage was not compatible with MVCC storages because the
  wrappers were being removed by each database connection.  There
  was also a problem with subtransactions.  Fixed.

----------

- Simplified the setup script in hopes of working with bdist_rpm.

- Fixed the setup test command.  It previously depended on private
  functions in zope.testing.testrunner that don't exist any more.

default to local host.

----------

- ZEO protocol 2 support was broken.  This caused very old clients to
  be unable to use new servers.

----------

- ZEO client threads were unnamed, making it hard to debug thread
  management.

to closs connection.  This showed up on windows but not linux or mac
os x. I wonder why.

cache and cleaning the cache.

shouldn't work reliably.  There's no text saying what it was for so
...

windows failures!

  Saving indexes for large file storages failed (with the error:
  RuntimeError: maximum recursion depth exceeded).  This can cause a
  FileStorage to fail to start because it gets an error trying to save
  its index.

counted properly.

avoid spurious test failures.

for a timeout.

Cleaned up code formatting.

cannot resolve.

(zodbguide) and published at http://docs.zope.org/zodb.