per-revision URLs (was: Re: First impressions...)

On Sat, Jan 26, 2002 at 09:59:13PM -0600, Karl Fogel wrote:
>...
> If humans get in the habit of doing something, pretty soon they're
> going to automate it. I think it's totally bogus for us to say "Fine
> for a person to type this in, but software should never depend on it."
> What kind of distinction is that? :-)

Fair enough. Mostly, I was just implying "if you *need* to, here is the
way". But your point stands...

> Is there any way we can canonicalize this format, i.e., declare that
> it will never change, at least in mod_dav_svn's implementation of
> WebDAV?

Not really. That '$svn' is subject to administrative control. I don't expect
anybody to create a file/dir named '$svn' in the root of their repository,
but since the server can define URLs how it wants, we let them control that,
just in case.

Regarding the /bc/REV/PATH part? Possibly. I worry about the REV part,
though, in case we introduce other kinds of baselines (thus, other kinds of
baseline collections).

It is safer just to avoid canonicalizing this stuff. It is discoverable, so
there isn't much need to define it up front.

> We're asking for trouble if people start depending on it and then we
> break it one day. Saying "Oh, well, you know we never promised..."
> won't cut it then. :)

I don't want people to depend on it today. The proper thing is to issue the
appropriate PROPFIND requests.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org