Re: RFC: a permanent svn-specific URL syntax

On Wed, May 28, 2003 at 03:59:38PM +0100, Colin Watson wrote:
| Something like this also allows access control to be used easily on both
| HEAD URLs and revision URLs. Using path-info as in "/revision" looks
| ideal for files because it ensures that it can't possibly clash with a
| real entry in the repository, but is not so good for directories.
| Perhaps "?rev=revision" would be simplest.

I agree that a CGI based method of specifying the revision is a good
way to implement this. This way, even if the feature is to disappear in a
future release, the URLs are carry the same meaning as now (assuming that
the CGI variables aren't re-assigned).

---
On a side note, please consider the expansion of $URL$ to take this
into account -- it is easy for the current $URL$ keyword expansion in
files (distributed to customers) to be invalid on a future date
(when a file/directory is renamed or deleted), although the
repository is still the same.
$URL$ can typically be a part of unused static char
strings -- something like rcsid[] typically used in builds distributed to
customers -- which can be listed using 'ident' on binaries (for example).
Instead of $URL$ expanding to:
$URL: http://developer.internal.site/repository/some/path/Complex.h $
it may expand to something like the following:
$URL: http://developer.internal.site/repository/some/path/Complex.h?rev=6018 $
Mukund
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org