XXX Maybe there should be an option to allow this.

A ZEO client can run in disconnected mode, using data from
its cache, or in connected mode.  Several instance variables
are related to whether the client is connected.

_server: All method calls are invoked through the server
   stub.  When not connect, set to disconnected_stub an
   object that raises ClientDisconnected errors.

_ready: A threading Event that is set only if _server
   is set to a real stub.

_connection: The current zrpc connection or None.

_connection is set as soon as a connection is established,
but _server is set only after cache verification has finished
and clients can safely use the server.  _pending_server holds
a server stub while it is being verified.

Before this change, a client could start using a connection before
verification finished.  If verification took a long time, it could
even commit a new transaction using a mixing of old and new data.

Pending does reads and writes.  In the case of server startup, we may
need to write out zeoVerify() messages.  Always check for read status,
but don't check for write status only there is output to do.  Only
continue in this loop as long as there is data to read.

test.

with StorageTypes.

conversion.

updated, which resulted in one whole cache being kept for no reason.

2 so they aren't normally run.

(ReconnectionTests make no sense for MappingStorage).

Also add BDBTimeoutTests.

Set the level for the FileStorageConnectionTests,
FileStorageTimeoutTests, BDBConnectionTests, BDBReconnectionTests, and
BDBTimeoutTests to level 2 so they aren't normally run.

MappingStorageConnectionTests and MappingStorageTimeoutTests both get
level 1 so they are normally always run.  FileStorageReconnectionTests
also gets level 1 since there s no MappingStorageReconnectionTests.

complete.

string to socket connect(), used 'localhost' instead).

much via the xmlmarkup environment definitions.

- add support for HTML generation

language, trying to set the pattern for the reference portion of that
section.

language.

since that function is no longer available, and was removed from the
documented API a while ago.

- normalized whitespace

This opens the door for separate database implementations to work nicely
with the ZConfig "ZODB" component.

no other handlers are provided.  This is needed to avoid warnings on stderr
from the logging package.

clear in the table of contents and section headings too.

  supported in the current version when using schema
- move the docs for the backward-compatibility modules to the end,
  nicely out of the way

Needs more work, but can deal with at least logging to files and STDERR.
Log rotation has been tested.

- add a way to control how logging is re-initialized

these were still used by the test suite. :-(

import to load the database and storage types.

- re-organize for easier reading

Placeholder for more tests.

XXX Maybe this belongs in BaseStorage.