-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David Binger wrote:
> Here is a thought.  Suppose you defined, very carefully, a subclass of
> Persistent that, in addition to doing exactly what Persistent does, also
> overrides attribute access and setting to put the oid into a set on the
> Connection.    You would also use a careful subclass of Connection
> that clears this set on every commit() or abort(), and uses it to
> avoid certain conflict errors.

I just read (again) the Durus license :-) and I could do a fork. But I
rather prefer an unified codebase };-).

I think we could change the durus codebase to be able to use the two
approaches WITHOUT penalizing "pure" read applications. Just add an
optional boolean parameter to "abort" and "commit", requesting
"ghostifing" the cache, as I already explained in other email. I can
elaborate the details, if you wish.

Applications that don't use the parameter (optional, no code change)
would work as ever, without performance hit.

> Thousands of objects.

Life was easiest with my Commodore VIC-20 :-p

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea@argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea@jabber.org         _/_/    _/_/          _/_/_/_/_/
                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRErT3Zlgi5GaxT1NAQLUKAP/aaMecIdiWvgdtzdpfEzGvSvUiL9g6P4X
EP+pzOWK3nMWqS+siJEvREiTA11LJ4W8dn6G6zEq6GCkwVtCrn+tnZ5+lMSG3wtl
nVbk7s1Y1BMddaecWHNw8irZDsY0raWN/n5BHO3nY1AufxWe2gsGZCRw0zjbxj8p
w8VFkWk8pc4=
=elZG
-----END PGP SIGNATURE-----