Hi,
Another reply:
How does this affect multiple processes accessing the same repository?
This caching looks like a nice speedup in some common cases, but I’m wondering
if we are adding new race conditions on revision property updates. We had to
add specific atomic revprop change apis to resolve/limit some older race
conditions and this looks at the surface like it might introduce a few new
cases.
Bert
From: Stefan Fuhrmann [mailto:stefan.fuhrm...@wandisco.com]
Sent: zondag 11 oktober 2015 14:26
To: Subversion Development <dev@subversion.apache.org>
Subject: Efficient revprop access in lib_repos
[This is the rationale and additional documentation to an upcoming
set of commits.]
When changing a revprop, we provide the following visibility guarantees:
1. A request that ends before the set_revprop started, sees the old value
(duh!).
2. A request that starts after the set_revprop completes, sees the new value.
3. A request that starts before the set_revprop completes, may see the old or
the new value and may not be consistent about it.
