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

Jesus Cea wrote:
> Current durus server receives a request, increments the rw-lock, calls

I have mixed the explanation. Current DURUS server doesn't have locks,
since it is non-multithreaded.

If you keep the server non-multithreaded, you don't need, either a
rw-lock. Just keep a counter telling how many reads are in progress.

> So the server can serve several simultaneous reads, keeping
> compatibility with not multithreaded backends. And the durus server
> doesn't need to be multithreaded either, important to keep the invalid
> notifications in sync.

David, I would volunteer for such a job if you agree in the
implementation :-).

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

iQCVAwUBRCB3e5lgi5GaxT1NAQK3EQQApYriAtl4Sb8F4peWhAbt5vLL/T3nHPes
dWgzzZ36QwDPjTgxyMEgf9bmZyedTBYYaEborrYajiC0M+BpRPN7viASuYBSPZJy
MkiwFHfDXDfQrGqKqN0KUgowJsguOI102GoeyKKivJaxhRrV11EWSM3ZJPxLVAfi
Vgyn0r42PRQ=
=PrGt
-----END PGP SIGNATURE-----