On 6/11/07, John Bäckstrand <[EMAIL PROTECTED]> wrote:
... It is still far from a perfect match though: I only care about having a few (2-10) mostly-trusted nodes, and not a whole lot about a DHT with the entire world which seems to be the point here...
actually, DHT's work best among a group of trusted peers. (see #2: groups of friends who want to share backup and file-sharing [0]) DHT's, like the 802.11 MAC, behave poorly when overly transient and/or malicious nodes are present.
I guess its possible to setup a private cloud though. I was imagining a very simple system where I specify for each file stored how much availability I want it to have, minimum, and then just store it on that amount of nodes
anything more than 3 or 4 reliable copies is not very useful for availability (odds of loss are very low, relatively) but might make sense for peak loads if you need to retrieve an archive via your FTTP line... :)
no fancy FEC nor DHT at all.
these are useful building blocks for distributed (and especially decentralized) computing. they make sense in this implementation, and hopefully usability is such that you don't notice this complexity when using it.
A good question of course is what happens when nodes go offline, but not a huge problem if you are actually using this together with a set of close friends.
the question is not if, but how many at once :) best regards, 0. Tahoe Use Cases http://allmydata.org/trac/tahoe/wiki/UseCases _______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
