Re: DHT traffic concerns

> * The expiration and republishing periods are way too small and
cause too
>   much republishing traffic.

I am doing some measurement about this. 
BTW, where can I upload files (e.g., graphs) to this forum.
 
> * The lack of usage of DHT STORE feedback (from the extended status code
>   list I published), driving the recognition that something is NOT rare
>   but actually quite popular.  I see too many STORE for some keys,
way too
>   many, and all these nodes must believe that what they publish is rare.
>   See next point.
> 
> * The determination that something is rare and needs to be published is
>   faulty.  The only real way to know something is rare is to try to
publish
>   it and see how many STORE_SC_FULL or STORE_SC_FULL_LOADED error
>   conditions you get back.
> 

As said earlier, I agree that it is a good idea to have clearer ERROR
code. 

Figuring out data popularity without creating much traffic is a
challenging problem. But I don't want to settle down with the idea of
using STORE requests to figure out popularity just yet. 


Best,
Peng