|
|
|
|
|
by philips
2545 days ago
|
|
I think this is a really compelling approach! What sorts of applications have started to adopt this? I also thought a different layer to start at would be sqlite databases since I understand that many mobile application use that. How do applications handle conflicts? It looks like there is a version on files but when is a new version created? On close? Do you see GDPR or any other compelling event that will cause applications to consider this sort of cloud storage? |
|
As there is transaction control, the conflict handling should be straightforward. That is, the thread got write lock can write the file exclusively and each write is a transaction and commit will form a new permanent version.
GDPR might be a good reason, but I think it can be more general. Any apps need store confidential data can use this, no matter the data is on local or cloud.