Re: Summary: URL rev proposals

Greg Stein wrote:
> On Wed, Aug 13, 2003 at 10:30:06AM -0700, Jack Repenning wrote:

>>>Sure, clients can do the transformation, but they might not "know" how to
>>>properly do that, and (certainly) web browsers are not going to be
>>>performing any such transformations.

But the server can certainly transform the "specify rev at end of URL"
model to a "specify rev at repository level", and could send a nice
"Permanently moved" HTTP redirect to that place.

>>>Further, if you eliminate the "specify rev at end of URL" model, then you
>>>are left with a revision in the middle somewhere. Now you have problems
>>>because the namespace in the middle is not clearly separate from the names
>>>of items that you can commit to that space.

Solved above.

>>Greg: is it fair to summarize this post as "there really is no
>>reasonable solution to this"?
>>(Not that I agree, actually, but is that what you're saying? ;-)
> Well, dang it... if you want to pin me down... yah :-)

I still think the proper solution is the one I suggested, with the
multiple revsion specifiers in the URL, but for simplicity reasons I
would recommend implementing the one with ..../repos;rev=STUFF/..., and
a http redirect for ....?rev=STUFF.

Note, that this simple approximation is a special case of my previous
suggestion, so if need arises the notation's implementation can be
generalized.

-- 
Helge
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org