On Sun, 27 Aug 2006, Max Bowsher wrote:
> Paul Cameron wrote:
>> Hello,
>>
>> I'm not sure if this should be posted to the users or dev alias, please
>> let me know if not appropriate for the dev list.
>>
>> I look forward to the new svnsync feature in 1.4. I see immediate
>> applications for repository backup via replication.
>
>
>> 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.
>
> My reasons for the alternate suggestion are:
>
> 1. Simplified user experience, they do not have to specify two URLs that
> must match.
>
> 2. Gives read-only server a hint that it should be looking for new
> changes to sync.
>
>
This would be EXTREMELY helpful in my situation as I've got a 2 - 3 GB
repository that is being used across the Internet, sometimes with big
(200-300 MB) updates. If we could set some property on a slave repository
that would re-direct clients to commit to the main repository then that
would be ideal.
Is this something that would be hard to implement? Something that would
be a great feature for 1.5?
--
David Wayne Summers "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = 0B44 B118 85CC F4EC 7021 1ED4 1516 5B78 E320 2001
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 27 23:29:22 2006