Thus said Richard Hipp on Sat, 18 Apr 2015 07:50:42 -0400: > When the artifacts that comprise a fork are received, the server has > no way of knowing that new artifacts that resolve the fork (either by > merging or by moving it onto a branch) will not be received within the > next few milliseconds.
I came to this realization as I was working on the sync-forkwarn branch. I abandoned the thought of having the server try to detect a fork for this very reason. It doesn't have all the necessary information to make such a decision, and indeed, the resolution of the fork may actually arrive in the next round-trip. So I removed that functionality. The only time that fork detection makes sense (if at all) is *after* a complete sync in the client. Andy -- TAI64 timestamp: 400000005532f19c _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
