agorise/graphenej
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Fix small issue in the NodeLatencyVerifier that caused incorrect (very small) readings to no-reachable nodes due to no internet connection.

Browse source
This commit is contained in:
Severiano Jaramillo 2018-09-27 11:33:18 -05:00
parent d109d86bf3
commit bb14110b09
1 changed files with 14 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
graphenej/src/main/java/cy/agorise/graphenej/network/NodeLatencyVerifier.java
View file

@ -22,7 +22,7 @@ import okhttp3.WebSocketListener;
public class NodeLatencyVerifier {
private final String TAG = this.getClass().getName();
public static final int DEFAULT_LATENCY_VERIFICATION_PERIOD = 5 * 1000;
private static final int DEFAULT_LATENCY_VERIFICATION_PERIOD = 5 * 1000;
// Variable used to store the list of nodes that should be verified
private List<FullNode> mNodeList;
@ -88,7 +88,7 @@ public class NodeLatencyVerifier {
long before = System.currentTimeMillis();
timestamps.put(fullNode, before);
// We want to reuse the same OkHttoClient instance if possible
// We want to reuse the same OkHttpClient instance if possible
if(client == null) client = new OkHttpClient();
// Same thing with the Request instance, we want to reuse them. But since
@ -145,9 +145,18 @@ public class NodeLatencyVerifier {
HttpUrl url = webSocket.request().url();
if(nodeURLMap.containsKey(url)){
FullNode fullNode = nodeURLMap.get(url);
long delay;
if(response == null) {
// There is no internet connection, or the node is unreachable. We are just
// putting an artificial delay.
delay = 10000;
} else {
long after = System.currentTimeMillis();
long before = timestamps.get(fullNode);
long delay = after - before;
delay = after - before;
}
fullNode.addLatencyValue(delay);
subject.onNext(fullNode);
}else{