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

Re: svn commit: rev 2554 - branches/issue-749-dev/subversion/include branches/issue-749-dev/subversion/libsvn_wc branches/issue-749-dev/subversion/libsvn_client branches/issue-749-dev/subversion/tests/clients/cmdline

From: Greg Stein <gstein_at_lyra.org>
Date: 2002-07-17 02:06:28 CEST

On Tue, Jul 16, 2002 at 06:12:18PM -0500, philip@tigris.org wrote:
> This got more complicated than I would have liked. I am still
> concerned about which directories get locked, and in which order they
> get locked.

What if you have a "WC session" object? That can store a hash of paths to
directory lock context objects. That way, you don't need to nest the things,
and you can (effectively) use random-access directory locking [instead of
strict parent-then-child operations].

It would introduce another open/close pair for the session, and then the
adm_open() call would take a session object.


Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jul 17 02:04:42 2002

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.