[bisq-network/bisq] Bitcoin p2p: Use different timeouts (#2609)

Manfred Karrer notifications at github.com
Tue May 14 21:41:06 UTC 2019


ManfredKarrer approved this pull request.

utACK

> @@ -87,7 +87,9 @@
 // Does the basic wiring
 @Slf4j
 public class WalletConfig extends AbstractIdleService {
-    private static final int TIMEOUT = 120 * 1000;  // connectTimeoutMillis. 60 sec used in bitcoinj, but for Tor we allow more.
+    private static final int TOR_SOCKET_TIMEOUT = 120 * 1000;  // 1 sec used in bitcoinj, but since bisq uses Tor we allow more.
+    private static final int TOR_VERSION_EXCHANGE_TIMEOUT = 125 * 1000;  // 5 sec used in bitcoinj, but since bisq uses Tor we allow more.

Is it intended to just have a slightly diff. value to TOR_SOCKET_TIMEOUT?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/2609#pullrequestreview-221276827
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190514/56a41020/attachment.html>


More information about the bisq-github mailing list