What I've done previously is to have the client log the the path and
hash in a local database (eg sqllite) after each file is synced. Then
when the sync finds differing client/server hashes it checks the db hash
to find out which, or both, has changed.
On 18/07/12 23:12, Sebastian Kügler wrote:
On Wednesday, July 18, 2012 10:31:13 Klaas Freitag wrote:
For that, the best would be if the ownCloud WebDAV server would provide
another WebDAV property that returns the md5-sum of the file or file
list. That probably means that the md5 sum needs to be calculated on
every file change on the server and be stored in the fs cache.
Is that doable? Who can help with that?
Naive question: If the md5sums differ, how do you know which file is older and
which one is newer?
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
