Re: svnsync - practical applications and plans

On 2006-08-27 08:11:34 -0500, Max Bowsher <maxb1@ukf.net> said:
>
> Paul Cameron wrote:
>
>> I feel another
>> interesting application would be for remote offices to perform all
>> 'non-commit' operations (log, update, etc.) against a local, replicated
>> server and commits against the remote, central server. The obvious
>> benefit would be much improved performance for non-commit operations
>> instigated from the remote offices. I believe this capability would
>> require clients that support two urls for the same repository. Is this
>> feasible and/or planned, or am I way off base here?
>
> That's actually a pretty interesting idea, though I'd submit the
> alternate design of the client only having one URL, and having the
> server either 'passing through' write operations to the upstream server,
> or issuing some sort of 'referral' to the client informing it to re-try
> against a different server.

It occurs to me that this could be done with Apache:

<LimitExcept GET PROPFIND OPTIONS REPORT>
    Redirect 302 http://server.to.write.to.com
</LimitExcept>

Does the svn client follow HTTP 30x redirects, perchance?

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