Changes between Version 35 and Version 36 of GSoCIdeas2010
- Timestamp:
- 2009-03-17T02:30:56Z (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GSoCIdeas2010
v35 v36 3 3 4 4 == Improvements to Tahoe == 5 * Dealing with NAT, ideally making it as easy to ignore as possible (taking advantage of upnp-igd and Zeroconf NAT-PMP) 5 * Dealing with NAT, ideally making it as easy to ignore as possible (taking advantage of upnp-igd and Zeroconf NAT-PMP). 6 6 * Opportunistic grid membership: 7 * Dynamic share migration to maintain file health8 * use Zeroconf or similar so nodes can find each other on a local network to enable quick local share migration7 * 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 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 10 * '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. 11 11 * Optimize upload/download transfer speed. 12 * Implement storage server protocol over HTTP. 12 13 * Make the [http://allmydata.org/trac/tahoe-w32-client Windows client] use only free open-source software 13 14