Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bluematt.me
	designates 173.246.101.161 as permitted sender)
	client-ip=173.246.101.161;
	envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; 
From: Matt Corallo <matt@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <201203131445.09552.luke@dashjr.org>
References: <CANEZrP17mwsmhShUKDOrZFsotLD+PHt6omNpL3-r21RtmHRX4Q@mail.gmail.com>
	<201203131445.09552.luke@dashjr.org>
Content-Type: text/plain; charset="UTF-8"
Message-ID: <1331668049.3266.0.camel@BMThinkPad.lan.bluematt.me>
Mime-Version: 1.0
Resent-From: Matt Corallo <bitcoin-list@bluematt.me>
Resent-To: bitcoin-development@lists.sourceforge.net
Date: Tue, 13 Mar 2012 15:48:02 -0400
Content-Transfer-Encoding: 7bit
Subject: Re: [Bitcoin-development] Adding a pong message
Precedence: list

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