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

Re: Older versions through http-repository browsing

From: Matthias Wächter <Matthias.Waechter_at_tttech.com>
Date: 2005-03-04 18:22:55 CET


"Peter N. Lundblad" <peter@famlundblad.se> wrote on 04.03.2005 17:04:56:

> What you see is always the HEAD revision. That's often useful and for
> files, it is what DAV requires.

Maybe, but it's not what I require :-)

> You could claim that the directory view is feature-freeze, but it is
> useful and it doesn't add much complexity. But we have to stop

Of course. It's not my point to add revision browsing, commit messages and
properties to the web interface. It's just selection of revisions using
reproducible URLs.

> Check out the viewcvs syntax, which at least I find more natural.
> Something like
> http://svn.collab.net/viewcvs/svn/trunk/contrib?rev=1490

Well, yes, that's better. It is more natural and close to what I want (I
knew someone would point me to a repo browser that is better in this
aspect) but that's not the point. I'd like to have an URL that directly
relates to a Subversion URI. Pedantic me :-)

> > WebDAV/DeltaV forbid to make the algorithm and naming behind PRIPFIND
> > requests public and that's the cause for this feature to be not
> > Some kind of unfair to those wanting to use the technique
> >
> I'm not sure efficiency was the main design criteria for WebDAV...

Well, then?

> > I don't like to have Subversion be a feature-creep repository-browsing
> > application as well. Maybe a plugin mechanism could help here? Any
> > not containing question marks is processed by standard Subversion, and
> > parameters are given, plugins could come into play that can help here.
> > Maybe then WebSVN or such could live transparently behind a Subversion
> > repository?
> >
> I don't see the point running them inside mod_dav_svn. What's the
> with running them separately?

It's a different URL. You have to give separate URLs for web-browsing and
for working with the clients. Why use URLs and WebDAV for the repository
at all?

> As seen above, it doesn't have to be cryptic. Regarding changing, the
> application could leave such guarantees. As a WebDAV server, subversion
> currently doesn't give you such a guarantee for the internal URLs.

But it could, couldn't it? The "?rev=" thing is not used for anything
AFAIK and will possibly remain unused as PROPFIND is all it takes. Why not
introduce this feature for this very purpose.

- Matthias

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 4 18:25:15 2005

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.