Re: Official revision syntax for Subversion URLs

John Locke wrote:
> I'm thinking along David's lines here--redirecting to a URL that
> includes the repository revision:
...
> Make the version fragment (after the semicolon) optional on the request,
> but ALWAYS return at least the semicolon in the response. For the HEAD
> revision, you can ask for:
>
> http://base.url/whatever/path/to/repos/path/to/file.ext
>
> And you get:
>
> http://base.url/whatever/path/to/repos;/path/to/file.ext

Furthermore, this could be just a backward-compatibility mechanism to help transition from the current status quo to a new URL syntax in which a semicolon is required between the repository and the path within it. In that new world, anyone accessing a Subversion repository by HTTP will already see where to insert a revision number.

There are other benefits to being clear about where your repository is, such as the "understanding what you are doing" class of arguments. As I said in another reply, this possibly ties in with a long-standing proposal to make the same distinction in working copy administrative data.

I can't see any problems with always having such a separator in a Subversion URL.

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 6 02:24:41 2003