Re: Summary: URL rev proposals

Greg Hudson wrote:
> I think this thread is about ready to wind down, so I'll summarize
> what I've seen, for the sake of people who didn't have time to follow
> it.

Thanks ;)

> A. We know from the past that some people want to be able to
> HTTP-browse their repositories

Serving web-sites, map http://foo/ to svn-dav, and svn copy new
releases, which have the added benefit of atomic site-updates :)

Browsing .html imported from releases.

> B. konqueror developers seem interested in adding a URL which means
> "visit a Subversion repository resource at rev foo using HTTP,"

"wayback"-mode, how did the world look before?

> C. It's possible that we might want to amend or change commands like
> [...]

Should be simple, and a nice symmetri.

> 1. Do nothing for now. Has some popularity at the moment.

Perhaps that will lead to the KDE ppl finding a good way to do it,
saving SVN the trouble :)

> 2. Add something to the end, whether it's "?rev=REV" or ";REV" or
> "@REV" or "@@REV" or "@@/REV".
> Issues: Relative browsing breaks

We can make answers to (for example) ?rev=REV as "301 Permanently moved"
to another syntax, for user benefit. Actually, if the client is a
browser, it move to the new URL.

> 3. Add something to the middle, between the location of the
> repository and the fs path.
>
> Issues: Given a normal HEAD URL, one can't algorithmically
> determine where to add revision information. Creates complexity
> when locations of repositories end with something which looks
> like a trailing version component (but that's not necessarily
> unreasonable).

Not really an issue, if we allow (2) to redirect as 301, you could
simply type in the "?rev=REV" syntax, and get redirected to the proper
syntax of this type (3).

The complexity of locations is not there if we use the URI
path-parameter specifier: ";", because URL's are required to escape
";"'s in paths anyway

with ";", we use the URI syntax with it's intended meaning.

> 3a. Add something to the middle for all URLs, including ones for the

I really don't like that, and i'm note sure how that would help.

> 5. Add something to the second-to-last path component (which might
> be the last path component of the repository location).

I'm not sure i understand that suggestion.

> 5a. Add something to any single path component.

Simply an implementation constraint on 5b?

> 5b. Add something to any path component; if multiple revs are

Exactly captures the possibilities you can express with the SVN
repository-model.

Together with "...?rev=STUFF" -> 301 to "repos;rev=STUFF/...", VERY
convincing!

My favorite :)

> Issues: Much too complicated.

Only complicated for the user if he uses the full expressive power

Implementation can be eased/limited by supporting at-most one ;rev=STUFF

> 6. In addition to one of #2-5, migrate to or add a URL syntax which
> Issues: Big change from current way of thinking.

Is this related to the core URL-rev problem?

--
Helge
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org