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

Re: repository GUIDs

From: mark benedetto king <bking_at_answerfriend.com>
Date: 2002-12-12 00:10:57 CET

On Wed, Dec 11, 2002 at 03:00:09PM -0800, Peter Davis wrote:
> On Wednesday 11 December 2002 14:43, Ben Collins-Sussman wrote:
> > should the GUID be attached to the
> > filesystem (accessed via libsvn_fs), as an unversioned rev 0 property?
>
> Just wondering, what would happen if someone changed that property? I can
> think of reasons why it would be good to allow changing it, and reasons why
> it would be bad. What (besides a "relocate" command) would rely on this?

I'm not sure exactly what you mean; relocate wouldn't need to change it,
just refer to it.

Adding the UUID in the repos gives two major benefits:

    1.) it lets the client validate that, barring malevolence, the
        repository its URLs point to is the one that was there before

and

    2.) it lets clients and servers use UUID/Node/Rev triplets to
        uniquely identify the chunks of data that they exchange; this
        is an important step in building a distributed repository
        scheme.

>
> If you store the GUID in a new file, then only someone with admin access to
> the repository's server can change it. People might want to tighten their
> pre-commit access control scripts to prevent normal committers from changing
> a revision property (either intentionally or accidentally), especially
> because it is unversioned.

Yes. This is a very important point, IMO.

--ben

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Dec 12 00:20:18 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.