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

Mike Orr wrote:
> However,
> if you're doing frequent writes, especially concurrently or modifying
> objects in place, you'll run into Durus's limitations.  But I've never
> seen Durus hang or crash.

Frequent writes (and huge datasets) are managed just fine if you use my
BerkeleyDB plugin for Durus. This comment goes also to Oleg Broytmann
email :-).

Concurrency (automatic, that is) is something I will address the day
after David implements fully the backend "sync" callbacks. Hope Durus
3.6 :-).

The main idea is to be able to "wrap" any storage in a "slim" (about 30
lines or less) proxy object, providing thread-safe, concurrent, durus
access.

David, please, implement "sync" :-)

PS: If full "sync" support is available in Durus 3.6, we will be able to
do things like replication, differential storage access (for example,
some clients only have readonly access), "caching only" (for load
sharing) durus servers, a durus server able to process several requests
at once, etc. These features will be implemented as backend plugins,
without touching any durus core code.

- --
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

iQCVAwUBRT0TTplgi5GaxT1NAQLQ4QP+KE7kkjr5MXt2gR+jEI7emVpkjA7WuskD
rmvrnTT0zPv6FGChMRg1yU0Fh1IkQe6XGfvs1DLCLIj/6y8woWaP1de2cyo3XE2p
+SiRv34hBHhnLg6btL9Ij7Qz8YkOkO0GJsW/LPPxM6liWko8A++K6NKirwtw0wRr
Gn3SXDKmjwU=
=kzkO
-----END PGP SIGNATURE-----