- Renamed updateCodeTimestamp() to resetCaches().

- Added a test of resetCaches().

- Removed a spurious comment about chaining connections together.

Patch from Dieter Maurer.

attribute was added in ZConfig 2.0, but I forgot to document it here.  :(

Bug fix candidate.

XXX Each record encodes the length of its oid.  Is it really possible
to have variable-length oids?  There's a high space cost for the oid
length, which is always 8 for the standard storage.

Also add docstring, copyright notice.

Add <warnfilter> section, which allows you to configure Python warning filters in zope.conf.  Useful for suppressing the USELESS DeprecationWarnings that emanate from TALGenerator wrt i18n.

XXX thought I already checked this in.

zope33_devel branch at this time.

configuration file can be used for both the runzeo and zeoctl scripts.
This makes it easier to keep all the configuration needed to support the
ZEO server process in a single file.
For more explanation of the changes, see
http://zope.org/Members/fdrake/WikiBlog/ZEOServerConfiguration

The file used to be called runsvr, but was changed.  Change the label
to RUNZEO to match the name of the file.

Add the process ID to distinguish different processes when tests are
running.

It looks like Connection refused errors in the test suite are the
result of a server taking a long time to get started -- usually when
the BDBStorage takes a long time to create.

transaction, not the position of the first record.

Not sure why this happens.

If you grep for just the Trans lines, it's probably more useful to
have the size than the offset.  Maybe.

and remove old comment about disconnected errors.

These are no longer used in Zope.

- remove commented-out cruftiness related to a no-longer-supported
  model

that the first thread to launch managed to commit each time, while the
other 3 threads got nothing but conflict errors.  Added some randomization
to boost the odds of success, and to prevent systematic favoring of any
thread.  That appears to work.