3 ms·
Very cool, I think I will try using this as my standard google drive solution on linux. One thing I haven't found in your paper is how the software handles con
by _hl_ 8y ago
Very cool, I think I will try using this as my standard google drive solution on linux.
One thing I haven't found in your paper is how the software handles conflicts. Suppose I have two or more machines hooked up to the same account, all simultaneously modifying the same file in different ways. What's going to happen? I guess this would be mostly up to the server side and out of your control, but maybe you can point me to a specification on how such issues are handled?
- harababurel 8y agoSome unwanted behavior might occur in scenarios like the one you describe. Most probably, the change performed by one client will silently overwrite the other. If there is however a small gap between the operations, the earlier one will have a better chance of being picked up by Drive and detected by the other file system instance. In this lucky case there might be no data loss. I would set the `sync_interval` configuration parameter to a low value to improve the chances of detecting changes as soon as they appear, but I would also try to make sure that only one client works on a certain file/directory at one time. This case looks like a good area for future improvement. Thank you for addressing the issue!