more ideas
[Imported from Trac: page GSoCIdeas2010, version 36]
parent
ca0adadab5
commit
a951ef26f3
|
@ -2,13 +2,14 @@
|
||||||
*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?*
|
*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?*
|
||||||
|
|
||||||
## Improvements to Tahoe
|
## Improvements to Tahoe
|
||||||
* Dealing with NAT, ideally making it as easy to ignore as possible (taking advantage of upnp-igd and Zeroconf NAT-PMP)
|
* Dealing with NAT, ideally making it as easy to ignore as possible (taking advantage of upnp-igd and Zeroconf NAT-PMP).
|
||||||
* Opportunistic grid membership:
|
* Opportunistic grid membership:
|
||||||
* Dynamic share migration to maintain file health
|
* Dynamically migrate shares to maintain file health.
|
||||||
* use Zeroconf or similar so nodes can find each other on a local network to enable quick local share migration
|
* Use Zeroconf or similar so nodes can find each other on a local network to enable quick local share migration.
|
||||||
* 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
|
* 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
|
||||||
* '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.
|
* '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.
|
||||||
|
* Optimize upload/download transfer speed.
|
||||||
|
* Implement storage server protocol over HTTP.
|
||||||
* Make the [Windows client](http://allmydata.org/trac/tahoe-w32-client) use only free open-source software
|
* Make the [Windows client](http://allmydata.org/trac/tahoe-w32-client) use only free open-source software
|
||||||
|
|
||||||
## Deep Security Issues
|
## Deep Security Issues
|
||||||
|
|
Loading…
Reference in a new issue