On Sat, 7 Dec 2002, Michael Loftis wrote: > The delay of writing 100+MB files out across the T-1 wouldn't be > acceptable. The writes occur pretty equally at both sites, with no clear > winner on that.
then i think you need something neither has, but coda could have more easily (if it doesn't; it might): lazy replication. write the file to the local replica and let it propagate later. this means no strong coherency. > So am I right in understanding that AFS doesn't allow multiple RW replicas? correct > You have one 'master' RW, then other RO replicas, and when a write occurs, > what, the whole file goes upstream, or only the changes from the clients it depends how you changed it. > cache? I understand the difficulties in having multiple RW replicas, the > locking issues, etc, but the concern is to try and keep from transmitting > entire 100MB files all the time and to allow both teams to work efficiently. _______________________________________________ OpenAFS-info mailing list [EMAIL PROTECTED] https://lists.openafs.org/mailman/listinfo/openafs-info
