From: Mike Hearn <mike@plan99•net>
To: Luke-Jr <luke@dashjr•org>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Adding a pong message
Date: Tue, 13 Mar 2012 23:29:27 +0100 [thread overview]
Message-ID: <CANEZrP3vRKiEBsosi1SaD=Sz-CZ7LqunwqURHSf=sYiNqfutNg@mail.gmail.com> (raw)
In-Reply-To: <201203131445.09552.luke@dashjr.org>
TCP keep-alives aren't reliably implemented.
I've got reports that sometimes we struggle to keep connection to the
network on mobile, eg, because we roam into an area with poor
connectivity but not poor enough for the network stack to drop access
entirely. Being able to quickly check if the connection is really
there with some kind of bounded, app layer deadline is probably useful
and besides, it's cheap.
prev parent reply other threads:[~2012-03-13 22:29 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
2012-03-13 22:29 ` Mike Hearn [this message]
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='CANEZrP3vRKiEBsosi1SaD=Sz-CZ7LqunwqURHSf=sYiNqfutNg@mail.gmail.com' \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=luke@dashjr$(echo .)org \
/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