diff options
| author | Matt Corallo <matt@bluematt.me> | 2012-03-13 15:48:02 -0400 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2012-03-13 19:48:13 +0000 |
| commit | 57f6c70f61f5588ec1b3d2e8e2a816cb781627ea (patch) | |
| tree | ba2adad61e61a4bf2660d254ae9e0ec03ebd1212 | |
| parent | 21ea68a12e5182f156f303d64fddf740408fce9d (diff) | |
| download | pi-bitcoindev-57f6c70f61f5588ec1b3d2e8e2a816cb781627ea.tar.gz pi-bitcoindev-57f6c70f61f5588ec1b3d2e8e2a816cb781627ea.zip | |
Re: [Bitcoin-development] Adding a pong message
| -rw-r--r-- | 6f/6c6bcd2086335caa6040caa514310fea8390b4 | 81 |
1 files changed, 81 insertions, 0 deletions
diff --git a/6f/6c6bcd2086335caa6040caa514310fea8390b4 b/6f/6c6bcd2086335caa6040caa514310fea8390b4 new file mode 100644 index 000000000..985deceee --- /dev/null +++ b/6f/6c6bcd2086335caa6040caa514310fea8390b4 @@ -0,0 +1,81 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <bitcoin-list@bluematt.me>) id 1S7Xhd-0003tM-Bp + for bitcoin-development@lists.sourceforge.net; + Tue, 13 Mar 2012 19:48:13 +0000 +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; +Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me) + by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) + id 1S7XhY-0002qd-UT for bitcoin-development@lists.sourceforge.net; + Tue, 13 Mar 2012 19:48:13 +0000 +Received: from [152.23.98.43] (dhcp04615.highsouth-resnet.unc.edu + [152.23.98.43]) + by mail.bluematt.me (Postfix) with ESMTPSA id 071DC156 + for <bitcoin-development@lists.sourceforge.net>; + Tue, 13 Mar 2012 19:46:05 +0000 (UTC) +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 +X-Mailer: Evolution 2.32.2 +Content-Transfer-Encoding: 7bit +X-Spam-Score: -1.3 (-) +X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. + See http://spamassassin.org/tag/ for more details. + -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for + sender-domain + -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay + domain + -0.0 SPF_PASS SPF: sender matches SPF record + 0.2 AWL AWL: From: address is in the auto white-list +X-Headers-End: 1S7XhY-0002qd-UT +Subject: Re: [Bitcoin-development] Adding a pong message +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Tue, 13 Mar 2012 19:48:13 -0000 + +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 + + + |