Repository UUID Implementation

1.) They're UUIDs, not GUIDs.

   APR calls them UUIDs.

   I prefer "UUID" to "GUID".

   We don't want to imply any terra-centric bias for svn. Xenophobia is
   an insidious form of bigotry that must be stamped out at the root. :-)

2.) They should be accessed via a New RA Method.

   They don't fit perfectly into any of the existing methods (for
   example, exposing them as distinguished rev-props complicates the
   rev-prop code-path).

   We'll probably eventually want to add repository metadata accessor
   methods to the RA vtable; we might as well do it now, before 1.0.

3.) They should be stored in a New FS Table

   They have to be stored somewhere. Storing them anywhere but somewhere
   new almost certainly means complicating the code that already uses
   the old location. "Somewhere new" means, basically, one of

        a.) a normal file, like the "format" file
        b.) an FS table

   For storing a single, rarely changing value, a normal file would
   probably be fine. Later, when we want to store other pieces of
   repository metadata (a text description, perhaps, to support "svn info
   URL"), or when we want to associate node-revisions with other
   repositories, we'll probably need a tabular persistence mechanism.

   We might as well bite that bullet now, rather than later.

--ben

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 9 02:00:44 2003