Managing delete / edit on the same tree item in a multi-user app (CRDTs)
I am trying to figure out the best solution for a distributed system in which I am dealing with a tree (to represent files in a file system). When User A deletes a file or folder, and User B renames the same file or folder (or a file contained in the deleted folder), when User A receives the edit from User B, the file or folder on which the operation is supposed to be performed no longer exists.
Managing delete / edit on the same tree item in a multi-user app (CRDTs)
I am trying to figure out the best solution for a distributed system in which I am dealing with a tree (to represent files in a file system). When User A deletes a file or folder, and User B renames the same file or folder (or a file contained in the deleted folder), when User A receives the edit from User B, the file or folder on which the operation is supposed to be performed no longer exists.
Managing delete / edit on the same tree item in a multi-user app (CRDTs)
I am trying to figure out the best solution for a distributed system in which I am dealing with a tree (to represent files in a file system). When User A deletes a file or folder, and User B renames the same file or folder (or a file contained in the deleted folder), when User A receives the edit from User B, the file or folder on which the operation is supposed to be performed no longer exists.