On Wed, Aug 6, 2014 at 2:14 PM, Richard Hipp <d...@sqlite.org> wrote:
> Advisory locks are used. So cooperating programs know to not have two > programs writing at once. But Dropbox is not a cooperating program in this > context. Dropbox just opens the file and writes, without paying any > attention to the advisory locks. > That's always been my assumption, but _somehow_ it avoids conflicting (if it sees a conflict, it creates two copies and lets the user sort it out, but i haven't seen that happen in about 4 years). My current hypothesis is that either the filesystem listener API watches the locks (since it's _presumably_ implemented at a level low enough to query the locking info), or that Dropbox tries, e.g., to get a write lock on a whole file, and simply aborts what it's doing if it cannot (under the assumption that someone else is using it). But that's all speculation. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
