On Fri, Apr 04, 2003 at 03:32:59PM -0600, Ben Collins-Sussman wrote:
> firstname.lastname@example.org (Martin v. L÷wis) writes:
> > Ben Collins-Sussman <email@example.com> writes:
> > > However, the svn client has to make a number of queries to 'discover'
> > > the correct URL to GET. The server has the right to define the
> > > resource space however it chooses; so the deltaV spec only defines a
> > > way for the client to query/discover the correct URL that represents
> > > the older file.
> > I see. But isn't it always the same format, for a subversion server,
> > i.e. <repository>/!svn/ver/<version>/<path> ???
> Well, at the moment, yes, the subversion server (mod_dav_svn) *does*
> have a fixed format. But that could change at any time. So clients
> still need to follow standard deltaV procedure to discover the URL.
Well, as Garrett pointed out, that format has changed in the past, so it
isn't "fixed" by any means.
Second, the "!svn" portion can be changed by the administrator. Some whacko
out there might want to have a file named "!svn" and we enable them to do
that. Or, the admin might simply want to have particular URL layouts for
something she is doing.
Third, the /ver/ resources are probably *not* what you want. Those access
specific resources at various points in time. To reach them, you have to do
a number of queries to get the right version resource (the current form of
rev/path is *very* subject to change; that one changed dramatically since we
started). To actually browse an older revision, the official DeltaV concept
is to browse a baseline collection (since we model revisions as baselines).
Those URLs are at .../bc/<rev>/.
Again, you should perform the appropriate PROPFIND requests to find the
baseline collection. Humans "in the know" can type it into their browser.
But I would not recommend encoding any of those paths into any software.
Always use the PROPFINDs within code.
Greg Stein, http://www.lyra.org/
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sat Apr 5 00:16:34 2003