-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Another suggested improvement for a future durus release.
Currently durus clients must issue a "new_oid" per new object created,
when doing a commit. Since no "new_oid" is requested until an answer
arrived for the previous one, this operation is fairly latency
sensitive. Commiting 100 new objects over the Internet can takes 10
seconds, easily.
We could add a new "new_oidS" command to request several OIDs with a
single command, so paying the latency one single time.
Would be nice other change: currently durus "loses" OIDs when a commit
fails (conflicts). That is, the OIDs given to the newly created objects
are lost. I think would be easy enough if those already assigned OIDs
would be pushed to an OID pool (local to that client) to get new OIDs
from, when it need them. Perhaps not a problem really, since we are
using 64bit OIDs (so, nearly "infinite"), and if we implement the
"new_OIDs" improvement, latency issues would be not a problem either.
Perhaps long running clients, with many new objects commits, could
"preallocate" OIDs using the "new" "new_OIDs" to fill the pool :-).
Client command pipelining would be nice too... to discuss some other
day. Latency is killing my Durus performance over Internet :-).
- --
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
iQCVAwUBRGlWj5lgi5GaxT1NAQKaXgP+KHs/NL8BP6h4+ny3Lcvpu/4N6TCxJi+7
tMtdyB4JE27MWsLf4RxNfaLxq5jEuJUi62SEU3FNVuR4ojJyuuoXQ3CJonxDQZPR
M54LW11Sh7qzjmLw/rZts1otYrOaf0c7jRl9KnQdcO6QWYY1JS9aUiPKNKRnDo7C
DaD607FwkiY=
=Wi7Z
-----END PGP SIGNATURE-----