From: Matt Corallo <matt@bluematt•me>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Adding a pong message
Date: Tue, 13 Mar 2012 15:48:02 -0400 [thread overview]
Message-ID: <1331668049.3266.0.camel@BMThinkPad.lan.bluematt.me> (raw)
In-Reply-To: <201203131445.09552.luke@dashjr.org>
On Tue, 2012-03-13 at 14:45 -0400, Luke-Jr wrote:
> On Tuesday, March 13, 2012 2:06:38 PM Mike Hearn wrote:
> > https://github.com/bitcoin/bitcoin/pull/932 adds a "pong" message that
> > echoes back a 64 bit nonce contained in the ping, if the protocol
> > version is new enough.
> >
> > The goal of this is to make it easier for clients, especially mobile
> > clients, to quickly check if a connection is stale, and also to see if
> > a remote node is overloaded so we can avoid talking to it. A common
> > case where this happens is if the remote node is itself downloading
> > the block chain or doing something equally intensive.
> >
> > Any objections?
>
> Not really an objection per se, but what's wrong with TCP keepalives?
>
It wont tell you if the node itself is overloaded (not just the OS'
network stack).
Looks good to me.
Matt
next prev parent reply other threads:[~2012-03-13 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 18:06 Mike Hearn
2012-03-13 18:45 ` Luke-Jr
2012-03-13 19:48 ` Matt Corallo [this message]
2012-03-13 22:29 ` Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1331668049.3266.0.camel@BMThinkPad.lan.bluematt.me \
--to=matt@bluematt$(echo .)me \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox