Hi Perry,
Perry E. Metzger wrote:
> Lets say you have an open source project where you want to have a lot
> of anon repositories. Have the main repository run an nntp server, and
> post PGP signed versions of all incremental changes to a special
> newsgroup. Run nntp on a tree of anon servers... and watch as the
> updates flood fill to all of them in seconds. Add some code which
> checks the signatures and applies the changes, and something to do a
> periodic last ditch consistency check (say posting cryptographic
> hashes of the whole repository every day or so) and you have an
> anonsvn infrastructure that scales to thousands of copies of the
> repository that are all nearly in sync in real time...
I like the basic idea (but could only be bothered to help when doing
it in python :-).
> If you find nntp too disgusting, some custom service could work the
> same way, but there's lots of good nntp code with high performance out
> there already, I figure...
For smaller setups maybe just triggering the peers to grab incremental
dumps from the master repo might be enough. This sounds simple enough
if we are dealing with three or four repository mirrors.
For massively distributed environments, like every developer
running his own repo, using bittorrents for wider distribution also
sounds worthwhile.
Then again, really interesting would be if you can actually commit to any
of the many repositories. ASFAIK the possible resulting merge conflicts
are not trivial to handle or to avoid unless you revert to some centralized
locking mechanism which defeats the massively distributed scenario and
leads to single point of failures. Also the uniqueness of revision numbers
will suffer and what not ... (someone will surely point out that
the documentation explains all this already :-)
cheers,
holger
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 19 18:06:41 2004