From: Jeff Garzik <jgarzik@exmulti•com>
To: Christian Decker <decker.christian@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bootstrapping via BitTorrent trackers
Date: Mon, 13 Jun 2011 12:51:02 -0400 [thread overview]
Message-ID: <BANLkTimTu3PNLTgv052-RZHHKTOUnrpT+g@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikbQpU8+NMT_-f2mVNe-cGLY-ZeuQ@mail.gmail.com>
On Mon, Jun 13, 2011 at 7:48 AM, Christian Decker
<decker.christian@gmail•com> wrote:
> The advantages over IRC and DNS Seeds are:
> - sporadic HTTP requests to a tracker, as opposed to keeping an IRC
> connection open at all times
No advantage over DNS (you're talking about IRC)
> - no virus/botnet like behaviour (automatically join IRC channel with
> cryptic name), ISPs tend to bother network admins (like myself) with alerts
> when they see this...
No advantage over DNS (you're talking about IRC)
> - adapts faster than DNS Seeds which require configuration changes on seed
> should the nodes become unreachable
False. A proper DNS seed actively samples the bitcoin network for live nodes.
> - we already use HTTP to determine our external IP, so it would be a
> consolidation of transports
Irrelevant -- it's still a bunch of additional code. We "already use"
DNS lookups as well, so I could apply similar logic to DNS seeding.
> - more peers than DNS Seeds (better load balancing)
This is an invalid assumption, based on an overly simplistic sampling.
DNS seeds are perfectly capable of returning new and useful peers on
each query.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti•com
next prev parent reply other threads:[~2011-06-13 16:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 8:55 Christian Decker
2011-06-13 9:09 ` Jeff Garzik
2011-06-13 9:38 ` Christian Decker
2011-06-13 9:56 ` Jeff Garzik
2011-06-13 10:54 ` Vladimir Marchenko
2011-06-13 11:48 ` Christian Decker
2011-06-13 16:51 ` Jeff Garzik [this message]
2011-06-13 18:00 ` Vladimir Marchenko
2011-06-13 18:41 ` Gavin
2011-06-13 20:16 ` Jeff Garzik
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=BANLkTimTu3PNLTgv052-RZHHKTOUnrpT+g@mail.gmail.com \
--to=jgarzik@exmulti$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=decker.christian@gmail$(echo .)com \
/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