Thus said Charles Curtit on Fri, 15 Aug 2014 14:25:24 -0000: > * speedy user interface for every one. (central or satellite office)
fossil ui should be speedy for all users regardless of their location. fossil syncing to local satellite offices should also be as quick as that local connection will allow. > * low use of bandwidth btw offices (meaning no user go and try to talk > to the central server from a satellite office). As long as you don't allow IP level access to the central office repo to anyone but the remote satellites, you should be fine there. Then you control how often and the satellites sync. Controlling the amount of bandwidth will be more challenging and not necessarily a problem set for Fossil. What if the remote satellite has a bunch of huge commits by their local users? Then when the satellite syncs to the central repo, there will be a period of time where all the satellites have to receive those changes and that will be a big bandwidth event. I suppose, however, that from the perspective of the central office, this will be relatively much less bandwidth than if the sum of all satellite users had to sync from the central repo to their own clones. > * ease of creation or suppression of a satellite office As long as users of the remote satellite office cannot connect to the central site, then you can prevent an entire satellite office from syncing content simply by disabling the satellite to central repo sync user. But how will you prevent a remote satellite user from syncing to a different satellite repository? Will you have a single set of users that are synced between satellites from the central repository, or will each satellite have it's own unique set of users? Once that problem is solved, how will you prevent two users in separate satellites from syncing between themselves? e.g. You and I could be configured to sync to satellite1 and satellite2 respectively, and I may have no access to satellite1, and then satellite2 becomes suppressed, however, I could setup my own fossil server and have you pull from it, and then my changes would get incorporated the next time you sync to satellite1. Or I could push to a server instance that you setup to achieve the same effect. This raises the question: what is the purpose of satellite suppression? Thanks, Andy -- TAI64 timestamp: 4000000053efb2c1 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
