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

Re: How can I setup two svnservers with svnsync and both should provide checkout and checkins

From: Michael Diers <mdiers_at_elego.de>
Date: Sun, 24 Apr 2011 13:20:49 +0200

Hash: SHA1

On 2011-04-21 13:58, Nico Kadel-Garcia wrote:
> On Thu, Apr 21, 2011 at 5:15 AM, Ian Wild <ian.wild_at_wandisco.com> wrote:
>> That sounds like a good translation to me. The maths gets complicated to put
>> it mildly, but I know Dr Yeturu's work is in some part at least based on
>> Paxos ( http://en.wikipedia.org/wiki/Paxos_algorithm ). AIUI we've got the
>> only implementation of this model that can guarantee the consistency and
>> ordering of transactions; important when you need your repositories to
>> remain identical on every site!
>> Ian
> *NOTHING* can guarantee this.. This is key to the difficulty of the
> "merge" process for multiple branches against a common trunk.


I believe you misunderstand how the repositories are kept in sync.

> Maintaining two sets of changes on distinct repositories that wind up
> altering the same set of text, or code, in divergent ways cannot be
> guaranteed to be resolved "correctly" by a mechanical process, because
> the process would have to "understand" the discrepancies and resolve
> them. It can be as simple as a copyright notice, whose changes
> represent social information outside the scope of the source control
> system, or code changes in a subroutine in one branch and the handling
> of the error codes generated by that subroutine in a distinct branch.
> It may do a much better *job* of this than other tools. That would be
> cool, tricky merges have always been an issue. But mere ordering and
> consistency is not sufficient, overlapping merges require attention.

While your observation regarding merging is correct, it does not apply
to the replication technique that WANdisco use in their product.

The network nodes handling the repositories are distributed, but not
isolated. The nodes actively agree on how to apply a proposed change to
their repository replicas, effectively avoiding the merge problem.

WANdisco provide a well-written White Paper explaining this.


- --
Michael Diers, elego Software Solutions GmbH, http://www.elego.de
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

Received on 2011-04-24 13:21:24 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.