Forban2.0

Jump to bottom Edit New page

Alexandre Dulaunoy edited this page Mar 7, 2014 · 1 revision

Work in progress

The current limitation of the initial experimental protocol

Duplication of data (the protocol is only relying on filenames)
Huge file cannot be synchronized on unstable network
File and peer cannot be easily trusted (except with the HMAC key but need too much setup for each user/participant)

Requirements for the forban 2.0 protocol

Files must be composed of chunks and reconciliation must be based on the chunks
Files must be based on their hashes (à la git)
Protocol must support the handling of chunks (to allow resume and out-of-order synchronization)
Trusting peers and file proposed must be integrated within the protocol

Ideas?

Reusing BitTorent protocols?
git dataformat?