--On Friday, December 13, 2002 10:17 AM -0600 Ben Collins-Sussman
<sussman@collab.net> wrote:
> Here's the original excerpt --
>
> (From http://svn.collab.net/repos/svn/!svn/bc/1/trunk/\
> doc/programmer/design/future.texi:)
>
> @node Mirroring Servers
> @subsection Mirroring Servers
>
> This is like the ClearCase multisite feature. Essentially, it is a
> redundant distributed repository. The repository exists on two or
> more cooperatively mirroring servers (each one presumably being
> close, network-wise, to its intended users). A commit from any
> user is visible on all the servers.
>
> The best way to implement this is by creating a ``hierarchy'' of
> Subversion servers, much like the DNS or NIS system. We can define
> a server @dfn{master} to contain the ``authoritative'' repository.
> We can then set up any number of @dfn{slave} servers to mirror the
> master. The slave servers exist primarily as local caches; it
> makes @code{reads} and @code{updates} faster for geographically
> disperse users. When a user wishes to @code{commit}, however, her
> delta is always sent to the master server. After the master
> accepts the change, the delta is automatically ``pushed'' out to
> the caching slave servers.
Yup, that's the model I independently came to. =)
Score one for the big brains. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 13 19:01:47 2002