News for hackers. Stuff that matters.
Re:Dropbox confirms that a bug within Selective Sync may hav... by jamwt on Saturday October 11, 2014 @12:16AM (#8441232)
> The sync heavy lifting in Dropbox is handled by librsync, or at least was at one point.

Nope, highly custom process that involves librsync very little. The sophistication of what has to be done to solve this problem well would probably surprise you.

Re:Dropbox confirms that a bug within Selective Sync may hav... by stephenr on Saturday October 11, 2014 @12:44AM (#8441282)
Isn't the desktop sync client built around the csync tool? http://www.csync.org
Re:Dropbox confirms that a bug within Selective Sync may hav... by general_failure on Saturday October 11, 2014 @12:37AM (#8441268)
Yeah, rsync != bidirectional sync.
Re:Dropbox confirms that a bug within Selective Sync may hav... by rakoo on Saturday October 11, 2014 @12:19PM (#8442511)
He wasn't talking about rsync the binary but rather about librsync [0], the library that allows you to calculate a diff between two byte arrays without needing the cooperation of the other side -- ie you can calculate an efficient delta to send to remote without needing remote to be online at the moment you calculate, and without needing the complete old version, only a signature of it.

A good example use of it is the rdiff tool that allows you to do exactly what I said before. A better real-world example would be duplicity [1] or rdiff-backup [2] that use librsync to de-duplicate backups, without needing access to the whole previous value, only a small signature of it.

[0] https://github.com/librsync/librsync

[1] http://www.nongnu.org/duplicity/

[2] http://www.nongnu.org/rdiff-backup/