Repository id's?
From: Kenneth Olving <Kenneth.Olving_at_frameworx.com>
Date: 2003-09-23 21:15:20 CEST
Keeping threads separate a bit...
Is there any notion of a unique repository id?
Reason I'm asking is the following: for initial work I might set up a small win32 server local to us with one local URL. We work a bit and eventually we realize that we're in a state that we can share the stuff - so I want to make the repo available on a 'public' URL. I may even switch architecture and go with our regular Solaris boxes. Ok, so I dump and load on the new machine.
Technically I might now make a case of saying that the just loaded repo is actually the *same* repo from an identification standpoint. Or, arguably, maybe it's not. At least, the new repo should be identifiable as 'coming from' another id. All this obviously comes from my CC/Multisite experience where I have multiple replicas that essentially are 'equal' and I know I can treat them as such, more or less.
In any event I might like to be able to identify for future tracking that any content I got from URL A is now fully accessible from URL B. Since I will store configurations listing URL's, going back in time and retrieving a really old config will then give a URL that no longer is in existence. Instead I might like to store not URL's but rather the unique id of the repo, and externally have a indirection mapping between id and 'current URL'. That would allow my tool to adapt to changing URL's with a reasonable degree of knowing that I'm looking at the 'right' thing. Sure, there are all sorts of subterfuge that could be done to break this, but I'm not looking for foolproof stuff, just an extra layer of catching unintended errors.
Hope I'm making sense...:-)
ken1
Kenneth Olving
o 212.905.3015
Everyone else has a cool sig, so I have a feeble one.
---------------------------------------------------------------------
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.