-----BEGIN PGP SIGNED MESSAGE-----
Martijn Faassen wrote:
> Hi there,
> On Thu, Jun 19, 2008 at 1:38 PM, Christian Theune <[EMAIL PROTECTED]> wrote:
>> We propose to keep both implementations around and allow to select which one
>> to use. We would extend the FileSystemHelper to abstract the two strategies.
> Could the default be to choose the more scalable one, or would this
> lead to backwards compatibility issues?
Perhaps the class-level default would be the old one, but the
constructor-argument-default the new? E.g.:
strategy = 'naive'
def __init__(self, strategy='scalable'):
self.strategy = strategy
Hmm, but OTOH, this is not likely a case where we have to worry about
old persistent data ;). I guess old config files need to continue
to work as expected, which means that the directory itself needs some
kind of metadata file which indicates the strategy: in that case,
the absence of the file would indicate the need for the BBB version.
Tres Seaver +1 540-429-0999 [EMAIL PROTECTED]
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
For more information about ZODB, see the ZODB Wiki:
ZODB-Dev mailing list - ZODB-Dev@zope.org