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

Re: WebDAV proxies and locking

From: Mark Phippard <markphip_at_gmail.com>
Date: Thu, 30 Jul 2009 17:11:53 -0400

On Thu, Jul 30, 2009 at 4:59 PM, C. Michael Pilato<cmpilato_at_collab.net> wrote:

> What would help here is a way for the client tools to (optionally) specify
> the desired lock token.  (Or, if not the client tools, at least some new
> 'svnsync copy-lock(s)' subcommand.)  Is that a sane thing to allow?  If not,
> is there some other remote lock replication approach that we can suggest to
> folks who need this?

FWIW, the lack of an ability to use some svnsync option to sync the
locks also makes svnsync unsuitable for maintaining a backup
repository or for using svnsync to migrate a repository to a newer
version. I believe there are lots of users that use svnsync for both
of these things today. But if a user also uses the lock feature, they
either cannot use svnsync for this, or must live with the loss of the
locks.

Which is a roundabout way of saying I would be in favor of adding
support for this to svnsync.

I suppose a user in the WebDAV scenario could then use the
post-lock/unlock/commit hooks to sync the locks? I am not sure how it
would scale or be implemented, or whether there are existing ra calls
that can be used to obtain/write the necessary information. But I
think it would be the ideal if it could be done.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2377147
Received on 2009-07-30 23:12:12 CEST

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.