tempfiles do *not* perpetually accumulate.  (TemporaryFile reliably is
removed when the program is done with it, under both windows and
unix.)

ClientCache.__init__(): Set up the first TemporaryFile, and set both
self._p file names to None, to signify use of temp files.

ClientCache.checkSize(): Switch over to other persistent cache file if
self._p has names, or a new TemporaryFile if they're None.

(I included some comments to the code i touched, to ease the passage
of anyone else who winds up on that path...)

for versions when non-version data was committed.


Fixed bug in invalidation of objects that were committed from one
version to another. The objects were not invalidated in the old version.

methods.

Added logic to handle case where object *only* has version data.

Made debug logging a tad more verbose.

Errors in pickling exceptions were misshandled, causing the server
to fail.

when server comes back.

Fixed totallu broken 'versions', 'commitVersion', and 'abortVersion'
methods.

Added logic to handle case where object *only* has version data.

Fixed bug in handling of data for objects created in a version
(for which there is no non-version data).

server to implement vote correctly.

argument and didn't work with FileStorages.

The -S option allows you to specify a module variable name that is
different from the storage name.  You can now include a '.py' suffix
in the module name, if you must.

missing so that other code doesn't have to check that it's there.
Removed one check and added assignment of storage tpc_vote method
in version support code.

integers that could lead to database corruption. Now all file position
computation is done with Python longs. Thanks to Shane Hathaway for
finding this.

Fixed a bug that could cause database corruption if transaction user
names, descriptions, or extension data exceeded 64K bytes. This was
due to the faulty assumption that struct.pack caught overflows, which
it doesn't. :(

Changed to use new tpc_vote protocol. This allows errors that occur
in the last transaction step to be caught during the first phase of
two-phase commit. For example, if we run out of disk space, we now
catch the problem early enough to recover from it.

_abort.

Added some comments.

split database XML export/import into separate module at Zope
application level, since it (currently) depends on Zope-specific,
rather than ZODB-specific code.

bypasses/takes-over transaction processing.

application level, since it (currently) depends on Zope-specific,
rather than ZODB-specific code.

error messages.

FileStorage from expanding to 2 GB.

previous packs. Packs to earlier times can cause data lossage.

of the startup invalidation protocol.

called from a separate thread than the async main loop. We only want
the async main loop to close our _call (rpc) object. Instead of
closing it directly, we call closeIntensionally(), which, in return,
requests that the async main loop closes it, via the select trigger.

when a transaction is about to be written. It would be bad if we
"flipped" the cache twice during a transaction, as we would have
incomplete transaction data.  Note that this means that we could
exceed the target cache size if the data for a transaction exceeded
the target size (/2).

Changed the way that the storage is closed. Our close method may be
called from a separate thread than the async main loop. We only want
the async main loop to close our _call (rpc) object. Instead of
closing it directly, we call closeIntensionally(), which, in return,
requests that the async main loop closes it, via the select trigger.

Added seek before write in invalidate method. Without this, strange
things happen on NT and solaris. (I was probably breaking a rule of
thumb that says never to do a write() right after a read() even though
tell() would indicate I was in the right place.)

Added logic to update the cache index on an invalidate.

Added a separate call to check the cache size so that we only check
when a transaction is about to be written. It would be bad if we
"flipped" the cache twice during a transaction, as we would have
incomplete transaction data.  Note that this means that we could
exceed the target cache size if the data for a transaction exceeded
the target size (/2).