Sorry, I should have been clearer. I wasn't objecting to Ivan's
suggestion, just confused about why he was thinking about building
URIs manually. :-)
On Wed, Oct 1, 2008 at 2:49 PM, Greg Stein <gstein_at_gmail.com> wrote:
> I'm with Ivan: put any path into the URL path, not as a parameter.
>
> On Wed, Oct 1, 2008 at 12: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?
>>
>> I'm focused on aligning our HTTP requests exactly with RA apis.
>> Every RA api takes an ra_session object which represents the 'root' of
>> a repository operation. Granted, it's not necessarily always the root
>> of the repository, but I think we should preserve the same concepts.
>> The HTTP request should be against a URI that matches whatever
>> ra_session is anchored on; if a &path parameter is present, then it
>> should considered relative to the anchor.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
>> For additional commands, e-mail: dev-help_at_subversion.tigris.org
>>
>>
>
---------------------------------------------------------------------
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-01 21:58:13 CEST