Is there lock mechanism in SOLID? Or is there way to implement resource locking? I think it would be useful because Pod’s resources might be accessed from multiple applications simultaneously.
And I’m also curious about guarantee about Pod’s behavior. Do every Pods guarantee that every file operation will be applied sequentially?
First application: Make a.txt then make b.txt.
Second application: Check existence of b.txt and then read a.txt
On second application, a.txt is guaranteed to exist when b.txt exists?
Hi, I know the Node Solid Server has some locking mechanisms but I’m unsure how comprehensive they are. The Community Solid Server has resource locking mechanisms defined explicitly in their implementation, but I believe it locks a resource branch rather than an individual resource. The Manas Solid Server also has specific resource locking, too. I’m not sure about the Nextcloud server.
Solid relies a lot on clients which should follow client-to-client protocols. In such protocols it’s also possible to impose the usage of any mechanisms like Conflict-Free Replicated Data Type (CRDT) for instance. Noel de Martin has already implemented CRDT like showed in this video notably at 4:05.