4 ms·
For the curious, the rsync algorithm is, at its core, ridiculously small[0] and involves rolling checksums. I just keep wondering why nobody (but Dropbox) bothe
by lloeki 10y ago
For the curious, the rsync algorithm is, at its core, ridiculously small[0] and involves rolling checksums. I just keep wondering why nobody (but Dropbox) bothers to implement it.
[0]: https://github.com/lloeki/rsync/blob/master/rsync.py https://github.com/lloeki/rsync/blob/master/rsync.py
- rakoo 10y agoThat's a really nice resource, thanks for the pointer. The ideas behind are actually used in multiple places, through the librsync project (https://github.com/librsync/librsync https://github.com/librsync/librsync). rdiff-backup and duplicity are 2 known examples, and surely in other projects as well.
- Chris2048 10y agoI believe gdrive allows you to store file properties: https://developers.google.com/drive/v3/web/properties https://developers.google.com/drive/v3/web/properties I wonder if you could add hashes and checksums to files in this way? The trick would be adding the server-side app service manage these.