On Jan 22, 2012, at 23:42, sureshkumar nandakumar wrote: > I hope currently we don’t have "Multisite" perception in Subversion. > In earlier we had a discussion with CollabNet and Windisco team. > Windisco team have a solution with Multisite concept. I am sure about > Subversion other support. > > Can anyone suggest me, whether Multisite Concept is incorporated with > Subversion or not. > Our clients are working in different countries, it would be great if > we have Multisite solution.
Subversion works on the idea of a single master repository. You can host it wherever you like -- perhaps the site where most of your developers are located, or the site with the fastest Internet connectivity -- but there is only one of them. You can additionally configure as many read-only slaves as you want. For example you could have a read-only slave at each site, other than the site where you have the master. The slaves can be configured to proxy write requests back to the master. Users at each site would then connect to the server at their site, and any read operations (like checking out, or looking at the log) would be fast. Write operations (like committing) will take a longer for those sites that have the slave copies and not the master. The concept of multiple master repositories is a special thing that the people at the WANdisco company have developed. You can pay them lots of money to use that software, and they will probably tell you many reasons why you need it. I recommend trying a normal Subversion setup, with a single master server (and if desired any number of slave servers) first, since the software to do that is free.
