📅 Original date posted:2017-03-06
📝 Original message: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
Tim Ruffing [ARCHIVE] /
npub1cm…dwkls
2023-06-07 17:56:54
in reply to nevent1q…nxer
Author Public Key
npub1cmt6gqyfw3sdngkq0wadtpe3kmgyyeld6ad0g2h5tar3kpzcrmpqddwklsSeen on
wss://relay.nostr.bandPublished at
2023-06-07 17:56:54Event JSON
{
"id": "cdb238d2d18198cb6e246efa3ff7222461d85a0aae9bd23674324b175ca1b55a",
"pubkey": "c6d7a400897460d9a2c07bbad58731b6d04267edd75af42af45f471b04581ec2",
"created_at": 1686160614,
"kind": 1,
"tags": [
[
"e",
"7d71aaf3aaa91e1454a25f4f9688ba685bebb747e49a8ad14b817de1aa470d06",
"",
"root"
],
[
"e",
"f4c97882f23dbe66a22373f42d2828f6e392ddfd53049694a93648aa1c3f2290",
"",
"reply"
],
[
"p",
"c6d7a400897460d9a2c07bbad58731b6d04267edd75af42af45f471b04581ec2"
]
],
"content": "📅 Original date posted:2017-03-06\n📝 Original message:On Mon, 2017-03-06 at 17:30 -0500, Tim Ruffing via bitcoin-dev wrote:\n\u003e \n\u003e That works but a standardized way of indicating that piece of\n\u003e information to the client is useful. Then the client can display a\n\u003e \"connection status\" to the user, e.g., an \"possible out-of-date\"\n\u003e warning like the warning sign in the Qt GUI when Bitcoin Core is\n\u003e catching up the network.\n\nWait, forget this reply, I mixed up the two issues of keepalive and\ndefinition of low, high etc... -.-\n\n1. Keepalive for longpolling:\nAs I said, this can be useful for an out-of-date warning. I don't know\nif this is better solved with TCP keepalive or on the higher layer.\n\n2. Definition of low, high:\nMy feeling is that there is nothing wrong with providing exact\ndefinitions in the BIP, i.e.., giving up the flexibility does not too\nhurt much. However all of this is a minor issue after all.\n\nTim",
"sig": "4be622ccd767acda9982372d40985f13c3b244e2188417562be00719311edf093d362b473bd2331e56ec8f8e3253940131b09e3f7c70748e0e8be0fb4636ef06"
}