FileTree CRDT for SAFE Network

Core Libraries
82

@happybeing so there’s something I’m unclear on that maybe you can test out, with the fuse filesystem template you created.

I’m curious what happens if the filesystem allows two dir entries with the same name to be created. Does fuse (or kernel) care?

My guess is that what would happen is:

  1. readdir() returns all names, so ls would show the dups. (unless some layer detects the dups and errors out?)

  2. lookup() can only return a single entry, so it would find first match and dup(s) ignored.

This would effectively make dups visible, but inaccessible.

I’m not suggesting this is a good approach in any way, I’m just kind of curious what would happen.

83

My guess would be that the filesystem implementation determines this behaviour and would detect and refuse to create a duplicate (as in directory exists). FUSE can just pass things through.

84

Related: discussion of providing access to the Safe peer-to-peer filesystem for Emscripten:

cc @danda