dht: make reannounce margin bigger, safer

Adrien Béraud authored 8 years ago and Simon Désaulniers committed 8 years ago

Attempt closest search and nearby searches
until we are too far instead of trying every
search.

Reannouncing margin going from 5 seconds to 10 seconds.

Schedule every storage maintenance independently,
to improve performance when there are a lot of storages.

bump visual studio support

log: add filters

* filter log entries with new method setLogFilter
* filter by node id, search or infohash
* add optional parameter to 'log' in dhtnode

* several clang related bug fixes;
* connectivity changes related enhancements;
* new "refresh" protocol primitive (not exposed to API);
* "permanent put" operation fixes/enhancements;
* fixed general efficiency issues;

Simon Désaulniers authored 8 years ago and Adrien Béraud committed 8 years ago

Historically, the next announce timing was based on the last acknowledgement
received from a SearchNode. This behavior was invalid since the 'refresh'
operation. In fact, for a given value that was "refreshed", its creation time
would differ from the announcer's info. Therefor, all search node's
reannouncing timings would differ, hence causing inconsistency on the network.

dht: appropriate time info in permanent put ops

Simon Désaulniers authored 8 years ago and Adrien Béraud committed 8 years ago

This operation requests a node to refresh a value's time_point information of
its lifetime begining. This is intended to fix the *permanent put* operation
which has been having syncing issues since the introduction of an enhanced and
lighter put operation.