Re: Re: DHT usage and requirement lists

[email protected] wrote:
> As for data lifetime,
> I think each publisher should be able to specify a TTL, capped to 24 hours max.
> And the STORE reply should indicate the TTL that was retained by the node
> (could be adjusted down if the remote node thinks it's too far from the key).

Good idea. Perhaps the TTL should be equal to the publisher's uptime (up
to a maximum of 24 hours)? That means the republishing overhead will
decrease exponentially the longer the publisher is online.

We should probably consider the overhead caused by very short-lived
peers - perhaps peers shouldn't start publishing their files in the DHT
until they've been online for 15 minutes (then republish after 15, 30,
60, 120, 240 minutes as suggested above).

Cheers,
Michael