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

Hi, everyone. The list is too quiet lately :-p. Here we have some food
for the mind.

I've become pybsddb maintainer last month. So now I "almost" control my
entire stack python+durus+my BerkeleyDB backend+pybsddb+BerkeleyDB.
Pybsddb is fairly behind supporting "recent" BerkeleyDB features, like
replication or MVCC (MultiVersion Concurrency Control). When pybsddb
supports replication, I will update my berkeleydb durus backend to
transparently (for durus applications) support replication, master
election, redundancy, etc. Will be "interesting" days.

In the meanwhile I was thinking that providing "two-phase commit"
natively in Durus would be very nice. I could allow replication "now"
and useful features like being able to use connections to several
unrelated durus storages in a single transaction, with full group ACID
semantic.

What do you think?.

- --
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.8 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBR8ayvJlgi5GaxT1NAQLVCwP+Jr22hD/aVEZnld5u4NNmIfDhpazW8Jgn
VwynVs5XIljqHiNUe0LOJOToMNPmbiZUPJUjnkVdzdwzaE2bKDXi90uKlRkWjggP
panKVMKNHQ83BuMMjE3wbK5JSUAW7T6CyFXDfn0hCzPaCHL9OBbvEJJZPniulb3U
CyqX+Q6M+ww=
=otqu
-----END PGP SIGNATURE-----