Re: Summary: URL rev proposals

On Thu, Aug 14, 2003 at 10:08:27AM +0200, Julian Reschke wrote:
> > From: Sander Striker [mailto:striker@apache.org]
> > Sent: Thursday, August 14, 2003 8:57 AM
> > Subject: RE: Summary: URL rev proposals
> >
> > ..
> > > So does this mean that the /!svn/bc/ format is stable, unless the server
> > > administrator chooses to over-ride it?
> >
> > No.
>
> If that *would* be the case (but I think it isn't) that would be a bug as
> far as RFC3253 is concerned:
>
> "Version Resource
>
> A "version resource", or simply "version", is a resource that contains a
> copy of a particular state (content and dead properties) of a
> version-controlled resource. A version is created by "checking in" a
> checked-out resource. The server allocates a distinct new URL for each new
> version, and this URL will never be used to identify any resource other than
> that version. The content and dead properties of a version never change."

The URLs that mod_dav_svn passes out are stable unless the administrator
goes in and monkeys it up by reconfiguring the SVNSpecialURI directive. It
could also change with a software upgrade (altho we have no intent to change
them at this point).

But outside of those actions, mod_dav_svn defines URLs for version resources
which are "infinitely" stable. We have code to label them as such, from a
caching perspective, but it is deactivated pending some further discussion
apparently.

That said, when I say "stable", I mean something different from John. He's
talking about a stable *format*, which is not true. Clients cannot depend
upon the /!svn/bc/ format. A client can depend upon the server redirecting
them to the right place, however (as Sander pointed out).

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