I agree with the incentives. In fact, if you don't have massive concurrent development in the same set of files, a multisite application is pretty hard to configure and maintain ...
And if the coverage does not intersect ... in fact, we switched to CRC (but we are here with CC7.0.1 here, CRC in 6.0 was not advanced enough). This means that you have a good connection, allowing your user to connect to a web server representing CRC, and which will access your vobs for them.
Your remote clients will either use the "bold" client (the Eclipse RCP ClearCase client talking to your CRC) or the web interface to configure their snapshots.
Another point that pushed us away from Multisite is the licensing system: you cannot convert a wob to a βtiered oneβ without using (more expensive) multisite licenses, even for your local users ...
Therefore, if you want to use only multi-site licenses for your remote users, you need to isolate your data in a multi-user vob and then replicate this data to a regular vob!
In general, I believe that Multisite is not the only answer to the development team of offshore companies.
BUT, that, as said, one strong power of a multisite mechanism is its ability to synchronize itself from a delta coming from different sources:
- regular packet reception
- files
- even a CD burned with the last delta can do it!
This means that if your connection is not always with a remote site, Multisite may be a valid option.
source share