"Perry E. Metzger" <perry@piermont.com> writes:
> The two strategies that have come to mind for me are to do an
> incremental dump after every commit, copying that to the anon
> repository -- but that would miss property changes (another reason
> I'm bringing up issue #1). The other possibility that came to mind
> is somehow sending the db transaction log files over to the copy
> and replaying them there, but I must confess I have little or no
> idea how to do that.
By the way, this brings to mind my favorite unimplemented project
that I've always wanted to do with CVS and now would like to do with
SVN -- I'm mentioning it here because I may never actually get enough
round tuits and other people might like the idea.
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...
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...
Perry
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 18 22:42:54 2004