You could also look at zsync, its just like rsync but works over http -
http://zsync.moria.org.uk/ - so that might fit better in a
webdav-centric environment.
there's a bi-directional java implementation of zsync here:
https://github.com/miltonio/milton2/tree/master/milton-client/src/main/java/io/milton/zsync
Both rsync and zsync require your server to either persist or generate
on demand the list of crc's that make up the file chunks.
On 18/07/12 22:54, [email protected] wrote:
"Klaas" == Klaas Freitag <[email protected]> writes:
Klaas> Hi, as you know our current syncing requires that both machines
Klaas> (client and ownCloud server) operate on exactly the same time
Klaas> because we use the file modification time to decide which file
Klaas> to sync where.
Klaas> Unfortunately for a couple of reasons we can not keep up the
Klaas> requirement of synced times any more, even if it might make
Klaas> sense.
Klaas> I investigated the last couple of days what we can do. If times
Klaas> between server and client just had a constant difference, it
Klaas> were doable, but thats not the case. Time difference is
Klaas> variable in real world and that means we can't use the mtime to
Klaas> decide any more.
I suggest taking a look at rsync. It uses size, name and mtime as a
rough check, then uses md5 in chunks to transfer just changed parts
Peter C
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
_______________________________________________
Owncloud mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/owncloud
