Re: [PATCH] Allow transparent slaves to handle REPORT?

On Oct 12, 2007 10:44 AM, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> Most of the REPORT methods are read-only and can be served by the
> slave using its copy of the repository. The one exception I can think
> of is getlocks. So, if we apply this patch, the getlocks report won't
> be proxied correctly - IOW, the slave will think there are no locks
> while the master actually does have a lock. Is this a big deal? Are
> sites that have geographically distributed mirrors going to be using
> locking anyway?

I think there is a way for masters to push out the lock db to the
slaves via the post-lock and post-unlock hooks, so this is doable for
those sites that wish to support locking and transparent proxies.

  The only other questionable report would be
> getmergeinfo - and this depends upon what svnsync/replay transfers
> across. Would the mergetracking info be the same on the slaves?

The gang on #svn-dev said, "Yes, it'd be the same."

Committed in r27157. -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 12 22:27:36 2007