Changes between Version 39 and Version 40 of GSoCIdeas2010


Ignore:
Timestamp:
2009-03-17T05:48:21Z (16 years ago)
Author:
zooko
Comment:

added GUI

Legend:

Unmodified
Added
Removed
Modified

  • GSoCIdeas2010

    v39 v40  
    22''What could a smart student do in one summer, if they didn't need to worry about getting a summer job to pay the bills?''
    33
    4 == Improvements to Tahoe ==
     4== Server Selection ==
     5//Which servers are connected to your client, and which of them have which shares of your files?//
     6 * Dynamically migrate shares to maintain file health.
     7 * Use Zeroconf or similar so nodes can find each other on a local network to enable quick local share migration.
     8 * Deal with unreliable nodes and connections in general, getting away from allmydata's assumption that the grid is a big collection of reliable machines in a colo under a single administrative jurisdiction
     9 * Abstract out the server selection part of Tahoe so that the projects in this category of "grid membership and server selection" can be mostly independent of the rest of Tahoe.  See also [http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:j74uhg25nwdpjpacl6rkat2yhm:kav7ijeft5h7r7rxdp5bgtlt3viv32yabqajkrdykozia5544jqa/wiki.html#2009-02-06 this note about standardization of LAFS].
     10 * Write a GUI to visualize and manipulate the set of servers connected and the set holding shares of files.
     11
     12== Networking Improvements ==
    513 * Dealing with NAT, ideally making it as easy to ignore as possible (taking advantage of upnp-igd and Zeroconf NAT-PMP).
    6  * grid membership and server selection:
    7    * Dynamically migrate shares to maintain file health.
    8    * Use Zeroconf or similar so nodes can find each other on a local network to enable quick local share migration.
    9    * Deal with unreliable nodes and connections in general, getting away from allmydata's assumption that the grid is a big collection of reliable machines in a colo under a single administrative jurisdiction
    10    * Abstract out the server selection part of Tahoe so that the projects in this "grid membership and server selection" can be mostly independent of the rest of Tahoe.  See also [http://testgrid.allmydata.org:3567/uri/URI:DIR2-RO:j74uhg25nwdpjpacl6rkat2yhm:kav7ijeft5h7r7rxdp5bgtlt3viv32yabqajkrdykozia5544jqa/wiki.html#2009-02-06 this note about standardization of LAFS].
    1114 * 'tahoe sync'. The proposed #601 bidirectional sync option would be great for using tahoe as we would with dropbox (http://www.getdropbox.com/). Like the latter, the user could have a daemon which keeps things in sync in pollings within a one or two seconds schedule (maybe using inotify for uploads). In practical terms an user could have many machines pointing to the same tahoe:dir, each machine mapping this resource to a local directory, and all these machines could then have their local copies in sync, via tahoe:dir. I think this is good when someone has many machines and alternates use between them, like a notebook, a home desktop and an office desktop, for instance.
    1215 * Optimize upload/download transfer speed.
    1316 * Implement storage server protocol over HTTP.
    14  * Make the [http://allmydata.org/trac/tahoe-w32-client Windows client] use only free open-source software
     17
     18== Free The Windows Client ==
     19 * Make the [http://allmydata.org/trac/tahoe-w32-client Windows client] use only free open-source software.
    1520
    1621== Deep Security Issues ==