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

Re: svn commit: r33366 - trunk/notes

From: Lieven Govaerts <svnlgo_at_mobsol.be>
Date: Thu, 02 Oct 2008 12:12:20 +0200

Ivan Zhakov wrote:
> On Wed, Oct 1, 2008 at 11:48 PM, Ben Collins-Sussman
> <sussman_at_red-bean.com> wrote:
>> On Wed, Oct 1, 2008 at 2:38 PM, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>>
>>> This is great. Only one thing I'm missing what is the reason to use
>>> repository root and encode path parameter in query args? From my point
>>> of it's much better to work on target URL, without knowledge of
>>> repository root. I mean:
>>> GET /repos/trunk/foo.c?cmd=get-file&r=23
>>> instead of
>>> GET /repos?cmd=get-file&r=23&path=/trunk/foo.c
>>>
>>> Because resolving repository root takes additional workaround unless
>>> we have working copy.
>> ? I don't understand. Who has to 'resolve' a repository root?
> (sorry for my english)
>
> I meant that serf often resolves real repository root using
> svn_ra_serf__discover_root() and then requests some properties like
> repository UUID only on root of repository.

You don't need the repo-root to get the UUID of a repo, you need to know
a path in rHEAD in that repo. Problem is, if you're working on
path_at_PEGREV where path does not exist in HEAD you don't know such a
path. So, as workaround, ra_serf first finds out the repository root
because that's the only path that's sure to exist in HEAD.

Lieven

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-02 12:12:32 CEST

This is an archived mail posted to the Subversion Dev mailing list.