On a nutshell: how about using a peer-to-peer network as a darcs repo? The idea is simple. Instead of having one central repository, we would have a number of interconnected machines (some would call it a cluster), i.e. developer machines that are interested on having access to the repo. Changes made (patches recorded) to one machine would get distributed to the others using a peer-to-peer network.
Using disconnected hosts and synchronizing afterwards would be possible but I think the system would work better if every machine was turned on and synchronized with the others. That way recording changes would be a local operation and would of course be faster than the network operation needed for centralized systems as CVS. The patch distribution would be made automatically (theorically, ther would be no more need to pull and push). Of course there are the usual issues with conflict resolving. I think this would avoid much the traffic on the server (in fact, there would be no server) and pulls and pushs would be much faster (for an interconnected developmetn team). Any suggestions? Cheers, Thiago Arrais _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
