Re: svn commit: r1331883 - /subversion/trunk/subversion/svnadmin/main.c
Daniel Shahaf wrote on Sun, Apr 29, 2012 at 12:58:56 +0300:
> stefan2_at_apache.org wrote on Sun, Apr 29, 2012 at 09:12:49 -0000:
> > Author: stefan2
> > Date: Sun Apr 29 09:12:48 2012
> > New Revision: 1331883
> > URL: http://svn.apache.org/viewvc?rev=1331883&view=rev
> > Log:
> > SvnAdmin should always have revprop caching enabled such that
> > the infrastructure is being set up to notify *other* processes of
> > changes done by e.g. setrevprop.
What happens if 'svnadmin1.7 setrevprop' is run while a 1.8 server is
running? Will the 1.8 server miss svnadmin1.7's changes because the
latter doesn't have revprop caching enabled?
> > Even if the revprop update infrastructure fails for some reason,
> > the impact on svnadmin is low because it imposes a small overhead
> > for some operations but the process will always see its own changes.
> > Foreign changes may or may not become visible to the tool while
> > it is running -- just as today.
> Perhaps the config API should allow people to enable "I will notify
> other processes of my changes" without enabling "I will cache revprops
> in memory"?
Received on 2012-10-15 19:11:01 CEST
This is an archived mail posted to the Subversion Dev