Ori Amiga: Programming the Mesh

My head is spinning..this very far reaching and very cool.  I would imagine the network infrastructure you are setting up to enable this is a monster.

For me, it will be interesting to see if this could be leveraged for digital rights management.  Something like associating licenses to a users Mesh instead of a specific device.

The mesh synchronization infrastructure essentially detects conflicts at the DataEntry level – so in the case of file synchronization, this happens at the file file/metadata level.  While the system is able to resolve conflicts “automatically” if needed, in general it leaves the conflict resolution logic to the application layer.  For example, using the scenario you describe below where “two users are working on something and one saves right before the other” – the mesh user experience (e.g., Live Folders) will prompt the user with information about the two conflicting files and allow the user to select how they would like to resolve the conflict.  This approach enables applications which are able to handle conflicts at different levels to apply the appropriate logic for their users.  In other scenarios where multiple users may be editing different DataEntries within the same Feed in the system – the system will automatically apply merge semantics for the changes.