Skip to content

Syncing questions #13

Open
Open
@giorgio-v

Description

@giorgio-v

(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.
  • Disabled automatic syncing (see http://community.remotestorage.io/t/what-are-remotestorage-js-public-requests/44/4)
  • 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

  1. The obvious one. Does my “test” prove anything? I suspect it’s conceptually flawed, but I don’t see where nor how
  2. If the test logic is sound, was it correctly set up, especially on the client side?
  3. 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!)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions