I have had good luck with SVN used in *very* geographically dispersed
locations over not-so-fast but decent connections to the centralized server.
Plus, the nature of SVN being able to do hot backups with both the BDB and
FSFS options means 24x7 availability. I wouldn't hesitate to recommend it
... you can go with SVK (which is an awesome tool btw), but given how well
SVN performs over a WAN by itself, I'm not sure the extra complexity would
be warranted (in some cases.) Mileage may vary.
On 7/16/05, Ben Collins-Sussman <sussman@collab.net> wrote:
>
> Suu Quan wrote:
>
> > Question is: what is SVN solution for teams working over long distance?
>
> Answer: SVN is designed for WAN. That is, it assumes network is a
> scarce resource and thus is optimized to use it as little as possible.
> It sends only file "diffs" in both directions over the network, and many
> commands are optimized to not use the network at all.
>
> Still, SVN has no database replication. It is a centralized system. If
> you're looking for a "distributed" system, try SVK
> (http://svk.elixus.org), which is a separate product that builds on top
> of Subversion's libraries.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Received on Sun Jul 17 02:18:28 2005