Changes between Version 11 and Version 12 of GSoCIdeas/Notes

Timestamp:

2010-03-28T19:21:59Z (14 years ago)

Author:

kevan

Comment:

--

GSoCIdeas/Notes

@@ -40 +40 @@
  * Explore running a Tahoe-LAFS grid over [https://torproject.org Tor] or [https://i2p2.de I2P] to provide anonymity to servers and/or clients.
  * Rescue the neglected C client library [http://allmydata.org/trac/libtahoeclient_webapi libtahoeclient_webapi].
+
+=== Medium sized Distributed Mutable Files (MDMF) ===
+
+Mutable files in Tahoe-LAFS have some significant limitations and
+performance issues, as discussed in
+[http://allmydata.org/trac/tahoe-lafs/browser/docs/performance.txt docs/performance.txt]. Users who aren't aware of these limitations are
+surprised when they find out that mutable files can't scale to large
+sizes without using unacceptable levels of memory, and that reading one
+byte of the file costs as much as reading the entire file. 
+
+A fix for this issue would essentially be fixing #393. That is,
+
+  * Developing mutable files that are segmented on upload, as with immutable files. Part of this would involve making sure that the way we currently ensure the integrity of the parts of mutable files stored on servers is adequate for your new design, and altering it if it isn't.
+  * Implementing efficient reading and writing of arbitrary spans of those mutable files.
+
+This would make Tahoe-LAFS less surprising to users, and allow mutable
+files to be used in more ways than they currently are.
+
+To learn more about this issue, you should first read
+[http://allmydata.org/trac/tahoe-lafs/browser/docs/performance.txt docs/performance.txt], so you're familiar with the performance problems
+with mutable files as currently implemented. You should also look at the
+[http://allmydata.org/trac/tahoe-lafs/browser/docs/specifications/file-encoding.txt file encoding specification], to understand how immutable files are
+segmented (since you'll be doing something similar with this project). [http://allmydata.org/trac/tahoe-lafs/browser/docs/specifications/mutable.txt The mutable file specification] may be informative as well.
+The mutable file upload and download code is in
+[http://allmydata.org/trac/tahoe-lafs/browser/src/allmydata/mutable mutable],
+and, for comparison, the immutable file upload and download code is in
+[http://allmydata.org/trac/tahoe-lafs/browser/src/allmydata/immutable immutable].