Timeout for the connection (low)(in)activity in getRange

[nemanja-boric-sociomantic]

The legacy clients have implemented the algorithms for making sure that all nodes are alive and sending traffic. It is implemented via means of monitoring the events when the individual nodes finish running the request and observing the time for the remaining nodes to finish. In the case when client sees that the individual node needs a long time to complete the request, it would "timeout" and it would stop the request.

Ideally, the client should have a mean of aborting the request on a connection that seems staled, without client needing to track the individual nodes behaviours.

[gavin-norman-sociomantic]

Timing out an individual request-on-conn has two aspects:

1. Like a full request timeout, the client could simply ditch the RoC and ignore any future incoming messages for it.
2. It would also be nice to send a message to the node, telling it to stop. (This would handle the case of active but slow connections.)

I'm not sure how these two things would work together.

[gavin-norman-sociomantic]

It seems like the simplest way to implement this is as a kind of automated, per-RoC stop, using the standard Stop protocol.

[gavin-norman-sociomantic]

As for the value of the timeout, we discussed starting out with a non-configurable sanity check timeout (60s, say). We can tweak this or make it configurable, if needed.

[gavin-norman-sociomantic]

This would help: sociomantic-tsunami/swarm#361