(Please note: I’ve already discussed some of these points on IRC, but I thought it was a better idea to open an issue here because it could be a specific problem or question about this implementation).
tl;dr
I’ve tried to induce a sync conflict but I haven’t been able to.
Details
Downloaded, installed, boostrapped and launch remotestorage-ruby.
Defined a remotestorage.js module which basically stores a blob using storeFile.
With browser A: logged in, uploaded version 1 of a file
With browser B: logged in, uploaded version 2 of the same file
With browser A: uploaded version 3 of the same file
At this point my expectation was to get a conflict. As far as I can see, A should recognize a mismatch between version 1, i.e. its local copy, and version 2 uploaded by B.
Questions
The obvious one. Does my “test” prove anything? I suspect it’s conceptually flawed, but I don’t see where nor how
If the test logic is sound, was it correctly set up, especially on the client side?
Finally, looking at the rails application logs I don’t see how a conflict could be prevented since it checks only if a node with a given path is present. Please note that I don’t know rails: I just looked at the SQL statements. Is it the expected behavior?
Hope this helps (and I hope to gain some understanding, too!)
(Please note: I’ve already discussed some of these points on IRC, but I thought it was a better idea to open an issue here because it could be a specific problem or question about this implementation).
tl;dr
I’ve tried to induce a sync conflict but I haven’t been able to.
Details
remotestorage-ruby
.storeFile
.At this point my expectation was to get a conflict. As far as I can see, A should recognize a mismatch between version 1, i.e. its local copy, and version 2 uploaded by B.
Questions
Hope this helps (and I hope to gain some understanding, too!)