On Tue, Oct 16, 2012 at 5:51 AM, Branko Čibej <br...@wandisco.com> wrote:
> On 15.10.2012 17:14, Stefan Fuhrmann wrote: > > However, if you have a long-running process like a server, that race > > condition extends now extends over its whole lifetime. I.e. once a > > revprop got read, any change to its value by a pre-1.8 tool may never > > get detected. > > Ouch. This seems wrong. I'd understand a design like this if the > long-running server were the only process accessing the repository, but > that has never been the case in Subversion. In this case, a cache that > can't detect out-of-band changes to the canonical dataset isn't very > useful. > *sigh* If you really have to use 1.7 tools on an 1.8 server, you can't use revprop caching. Most people, however, will use 1.8 svnadmin on 1.8 servers. -- Stefan^2. -- * Join us this October at Subversion Live 2012<http://www.wandisco.com/svn-live-2012> for two days of best practice SVN training, networking, live demos, committer meet and greet, and more! Space is limited, so get signed up today<http://www.wandisco.com/svn-live-2012> ! *
