From: Brian Warner Date: Fri, 1 Dec 2006 00:16:19 +0000 (-0700) Subject: add roadmap X-Git-Tag: tahoe_v0.1.0-0-UNSTABLE~535 X-Git-Url: https://git.rkrishnan.org/%5B/frontends/%3C?a=commitdiff_plain;h=9d2aaf76085155a2c65b2d7dbfbad10beb07249d;p=tahoe-lafs%2Ftahoe-lafs.git add roadmap --- diff --git a/roadmap.txt b/roadmap.txt new file mode 100644 index 00000000..57c8a100 --- /dev/null +++ b/roadmap.txt @@ -0,0 +1,37 @@ + +Connection Management: Brian + v1: foolscap, no relay, live == connected-to-queen, broadcast updates, full mesh + v2: live != connected-to-queen, connect on demand + v3: relay? + +Encoding: Zooko + v1: fake it (replication), no merkle trees + v2: mnet codec + v3: merkle tree to verify each share + v4: merkle tree to verify each segment + +Peer selection: + v1: permuted peer list, consistent hash + +filetable maintenance: + v1: steal webfront code, encodingsdb, queen.set_filetable_uri + +checker/repairer: + v1: none + v2: centralized checker, repair agent + v3: nodes also check their own files + +storage: RobK + v1: no deletion, one directory per verifierid, one owner per share, + leases never expire + v2: leases expire, delete expired data on demand, multiple owners per share + + +back pocket ideas: + when nodes are unable to reach storage servers, make a note of it, inform + queen eventually. queen then puts server under observation or otherwise + looks for differences between their self-reported availability and the + experiences of others + +big questions: + convergence?