Improvement: use rolling checksums for files about clearskies HOT 3 CLOSED

There is an optional extension for rsync. I didn't put this in the core protocol to keep it simple to implement.

Your point about the sha256 hashing is interesting. In the proof-of-concept ruby app, we're debouncing file events to reduce the amount of recalculation, but that approach won't work for a slow file download that is being written less often than the debounce interval. I will add a recommendation for implementations to limit how often they will rescan a file in a manner similar to how often they should rescan a directory, as is mentioned in the third paragraph of the "Computer Resources" recommendations.

Thank you for reading over the spec so carefully!

from clearskies.

Yes I guess it's better to go keep it simpler and have it as an extension. Is anywhere defined a method for the clients to exchange the list of supported extensions?

from clearskies.

Extension negotiation is handled in the initial handshake. It's called "features" in there, which would probably be better if it were called "extensions", since apparently that's the name that I've been using in my head.

from clearskies.