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

Re: RFC: a permanent svn-specific URL syntax

From: Greg Stein <gstein_at_lyra.org>
Date: 2003-06-02 06:58:50 CEST

On Wed, May 28, 2003 at 08:50:42AM -0700, Justin Erenkrantz wrote:
> --On Wednesday, May 28, 2003 5:31 PM +0200 Rafael Garcia-Suarez
> <raphel.garcia-suarez@hexaflux.com> wrote:
> >The simplest safe short solution is probably to use a # sign (ie. the
> >uri fragment syntax) :
> > http://svn.something.net/repository/project/branch1/file.c#1613
> >It has the same advantages than the path-info solution, but works for
> Eww. No. # are fragments and not really part of the resource, but part of
> the representation. # are usually interpreted by the client not the server.
> The next rev of the URI spec will explicitly call fragments out, but it's a
> landmine we don't want to go near. -- justin

And just to continue shooting this stuff down...

The ?rev=whatever form is not appropriate. The query string is applied to
the resource specified by the other parts of the URL(*). i.e. it implies
there is *one* resource receiving different query values. But that isn't how
this stuff should be modelled -- we've got multiple resources. There is one
for each revision. Thus, the revision number should be part of the path
portion of the URL to get the proper modelling.


(*) see section 3.4 of RFC 2396

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
Received on Mon Jun 2 06:55:52 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.