- to use with
- to use call_from_thread
- to try to recover from errors (that should never happen:)

Added timeout thread liveness to server status

- Improved ZEO server commit lock logging.  Now, locking activity is
  logged at the debug level until the number of wating lock requests
  gets above 3.  Log at the critical level when the number of waiting
  lock requests gets above 9.

- ZEO servers no longer log their pids in every log message. It's just
  not interesting. :)

debugging easier.

failures.

Also made the disconnected in transaction messages show the locked
status.

https://bugs.launchpad.net/zodb/+bug/435547

set object state when objects implemented _p_invalidate methods
that reloaded ther state (unghostifiable objects).

https://bugs.launchpad.net/zodb/+bug/428039

http://pypi.python.org/pypi/zope.mkzeoinstance

and is no-longer included with ZODB.

with Python optimization turned on.

https://bugs.launchpad.net/zodb/+bug/544305

mapping storage when none is given.

- Added a '--kill-old-on-full' argument to the backup options:  if passed,
  remove any older full or incremental backup files from the repository after
  doing a full backup. (https://bugs.launchpad.net/zope2/+bug/143158)

the fan-out to fail.

When transactions are aborted, new object ids allocated during the
  transaction are saved and used in subsequent transactions. This can
  help in situations where object ids are used as BTree keys and the
  sequential allocation of object ids leads to conflict errors.

and colapsed some undo methods.

locks.

In fixing, also made it work with with.

Make lock non-private so subclasses can use it with with.

Use a more informative temporary file name.

The rpc manager can be called from the client loop if there is an error in
the client loop.

Need to call set_sender on tpc_finish result to get proper cleanup

Added a missing method

client loop.  Now the _rpc_mgr close should take care of closing
cleanly.

to avoid spurious test failures.

Fixes https://bugs.launchpad.net/zodb/+bug/516653 .

compiler silliness, but due to a threading bug which has been fixed.