1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
Return-Path: <tim.ruffing@mmci.uni-saarland.de>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 7B642416
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 6 Mar 2017 22:38:27 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from hera.mpi-klsb.mpg.de (hera.mpi-klsb.mpg.de [139.19.1.49])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E21C2204
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 6 Mar 2017 22:38:26 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=mmci.uni-saarland.de; s=mail200803;
h=Content-Transfer-Encoding:Mime-Version:Content-Type:References:In-Reply-To:Date:To:From:Subject:Message-ID;
bh=xaV4a60oJ+tuGG9tKwF+9CDIxThSmMpfhnV+SexJvFE=;
b=hqgf2WLtMC1Pa6GzseCuoYIKo59hFavOWSntHTi7AFmxzy+huHjwBsvwmxQehiZXgCgJPsAN42jHa5GuzkL8n92bJEy5/ptooZ/EA5uUz/EpjPXrvAowKRx0QGvszjgMcbq6oQLvZMIlGclThd7dQZ2KntregwnhBnyzgxDSIJ0=;
Received: from sam.mpi-klsb.mpg.de ([139.19.86.26]:58414)
by hera.mpi-klsb.mpg.de (envelope-from
<tim.ruffing@mmci.uni-saarland.de>)
with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128)
(Exim 4.80) id 1cl1Go-00059D-I2; Mon, 06 Mar 2017 23:38:25 +0100
Received: from [192.31.0.5] (port=63972 helo=[192.168.25.175])
by sam.mpi-klsb.mpg.de (envelope-from
<tim.ruffing@mmci.uni-saarland.de>)
with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.84_2) id 1cl1Gn-000Pl1-Ud; Mon, 06 Mar 2017 23:38:22 +0100
Message-ID: <1488839905.2134.7.camel@mmci.uni-saarland.de>
From: Tim Ruffing <tim.ruffing@mmci.uni-saarland.de>
To: Tim Ruffing <tim.ruffing@mmci.uni-saarland.de>, Bitcoin Protocol
Discussion <bitcoin-dev@lists.linuxfoundation.org>
Date: Mon, 06 Mar 2017 17:38:25 -0500
In-Reply-To: <1488839459.2134.5.camel@mmci.uni-saarland.de>
References: <201703040827.33798.luke@dashjr.org>
<201703060709.40311.luke@dashjr.org>
<1488837256.2134.1.camel@mmci.uni-saarland.de>
<201703062214.47660.luke@dashjr.org>
<1488839459.2134.5.camel@mmci.uni-saarland.de>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.22.5
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-MPI-Local-Sender: true
X-Spam-Status: No, score=-4.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Currency/exchange rate information API
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Mar 2017 22:38:27 -0000
On Mon, 2017-03-06 at 17:30 -0500, Tim Ruffing via bitcoin-dev wrote:
>
> That works but a standardized way of indicating that piece of
> information to the client is useful. Then the client can display a
> "connection status" to the user, e.g., an "possible out-of-date"
> warning like the warning sign in the Qt GUI when Bitcoin Core is
> catching up the network.
Wait, forget this reply, I mixed up the two issues of keepalive and
definition of low, high etc... -.-
1. Keepalive for longpolling:
As I said, this can be useful for an out-of-date warning. I don't know
if this is better solved with TCP keepalive or on the higher layer.
2. Definition of low, high:
My feeling is that there is nothing wrong with providing exact
definitions in the BIP, i.e.., giving up the flexibility does not too
hurt much. However all of this is a minor issue after all.
Tim
|
