On 5/8/07, David Irvine <[EMAIL PROTECTED]> wrote:
How do I actually store the file ?
It sounds like want to do this indirectly, i.e., you store a record in the DHT that points to the location of the file, but the file is not stored in the DHT itself. If that's the case, you just need to choose some other mechanism for transferring and storing files.
What if the nodes holding the pointer to the file disappear ? Can I make several copies of the pointer to confirm there ok ?
In most DHTs, including Kademlia, there is a replication factor. When you store a value to the DHT, it is stored N times, on N different hosts, usually at the N closest hosts to key ID. These locations need to be updated periodically, both because some of the N nodes may leave the network, and because newer nodes joining may end up closer to the key in the key ID space.
HOw can I get nodes to broadcast their timezone or other info such as rank - type of node etc. ?
DHTs maintain their own routing information with tables indicating how to connect to other nodes. You'll need some sort of bootstrapping for introducing nodes when they first join. You could certainly modify the routing tables to contain additional information about known nodes, such as TZ and rank, but it might be more useful to store some of this info in the DHT as well. But I'm not sure that a DHT is the right place to store a global list of all available nodes, if that is what you are after... BTW, the answers to all your questions (and many more!) can be found in papers such as those found at http://citeseer.ist.psu.edu/529075.html and http://pdos.csail.mit.edu/chord/pubs.html Alen _______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
