[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Official revision syntax for Subversion URLs

From: Jerry Haltom <wasabi_at_larvalstage.net>
Date: 2003-08-06 21:17:36 CEST

I like this idea... using a special character in the first path element
to represent the version. Preferably some character that isn't a special
char in most default shells.

http://url/path/to/svn/@123/path/to/somefile.html

This has the benefit that it works with the browser thing, a feature
that probably won't be used often, or at all. But is still cool. :D

Seems easy to implement too, the code must have the repos url at some
point, just stick in an 'if first char = "@" then strip off first path
and use number for revision.

Special things like @HEAD could be used to.

I'm not sure why other access methods than the HTTP GET have to be
concerened with this at all actually? Actual svn client library
functions use GET on the !svn path I thought. So, this doesn't effect
them, and is only a convient mapping for browsers or other GET using
utilities?

On Wed, 2003-08-06 at 14:06, Russell Yanofsky wrote:
> Jack Repenning wrote:
> > At 10:24 PM -0400 8/5/03, Martin Ayotte wrote:
> >>
> >> Some people says...
> >
> > Huh. Well, I think all of those people you quote are me :-) And you
> > left out one of my arguments, and I think failed to engage another
> > quite head on.
> >
> > The missing argument: what do you say about the problem of relative
> > hyperlinks buried inside a versioned HTML document? That is, if
> > http://host/repo/path/foo.html@@17
> > is an HTML document containing
> > <a href="../elsewhere/otherpage.html">
> > ... then it would be good if clicking that link in the displayed page
> > reached "otherpage.html@@17", not "otherpage.html@@HEAD". But that
> > decision will be made by the browser, not by SVN, and browsers don't
> > have built-in rules to carry "@@17" around like that. But they DO
> > have rules to link from
> > http://host/repo/r17/path/to/foo.html
> > via
> > href="../elsewhere/otherpage.html"
> > to
> > http://host/repo/r17/path/elsewhere/otherpage.html
> >
> > Someone was horrified that I would expect this to work. Why should I
> > not? It *will* work, so long as we don't make any mistakes right
> > here in this discussion, it's immensely useful, and it's how the web
> > works.
>
> I agree that this is a really nice feature, but it wouldn't say it's
> immensely useful. The only case I can think of where it would be useful is
> viewing a repository of static html files with relative links. Are any there
> other applications for this?
>
> - Russ
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org

-- 
Jerry Haltom
Feedback Plus, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 6 21:18:29 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.