[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2007-10-12 20:03:30 CEST

On Oct 12, 2007 10:50 AM, Mark Phippard <markphip@gmail.com> wrote:
> I think it is reasonable to assume the answer is Yes, they will be
> using locking. How would this manifest to a user? svn lock would
> presumably still need to lock at the master so wouldn't it still
> correctly fail if someone else held a lock? What commands use
> getlocks?

The LOCK and UNLOCK requests would get sent to the master - but lock
discovery would fail as the slaves wouldn't know about the locks.
Hence, the user would need to issue a force unlock to break it.
Locking would still work - it just would never get reported properly
as having a lock held via the APIs.

> If the request is a REPORT is it possible to peek inside the request
> to learn more before deciding to proxy it?

Nope. We have to make the decision based on the request lines and
headers - once we start reading the body, it is too late to make a
decision to proxy the request. -- 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 20:03:38 2007

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.