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

Re: Locking functional spec: read-only WC

From: John Peacock <jpeacock_at_rowman.com>
Date: 2004-10-13 20:54:33 CEST

Ben Collins-Sussman wrote:
> Oy, inherited properties?? Now you've spun us off into a whole new
> dimension of complexity!

How better to handle directory locking? I'm not saying that we have to
go that direction initially, but rather that the possibility shouldn't
be ignored in the design phase, just because we are not ready to
implement it immediately.

As long as the client code is completely ignorant of what is going on
with the server:

CLIENT: is this file locked?
SERVER: No, and here is a lock token!


CLIENT: is this file locked?
SERVER: No and the admin told me you cannot lock it!

then how it is actually stored in the repository is much more flexible.
  Now, it is a property associate with each and every file in a
directory; later, it could be an inherited property associated with the
containing directory.


John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 13 20:55:00 2004

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.