From: Jeff Garzik <jgarzik@exmulti.com>
To: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: [Bitcoin-development] Proposed new P2P command and response: getcmds, cmdlist
Date: Fri, 15 Jun 2012 20:13:21 -0400 [thread overview]
Message-ID: <CA+8xBpdD31koaVBh1RuDZKH1sygr8z10K=bPz8DepqYOa8i6yg@mail.gmail.com> (raw)
Outside of major features advertised network-wide in nService bits,
P2P protocol lacks a good method of enumerating minor features or
extensions. The version number increment is coarse-grained, and is
not self-documenting. A simple extension which lists supported
commands is added, as demonstrated in this pull request:
https://github.com/bitcoin/bitcoin/pull/1471
Another option is for verack to return this information at login,
eliminating the need for a separate command/response.
--
Jeff Garzik
exMULTI, Inc.
jgarzik@exmulti.com
next reply other threads:[~2012-06-16 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 0:13 Jeff Garzik [this message]
2012-06-16 1:34 ` [Bitcoin-development] Proposed new P2P command and response: getcmds, cmdlist Amir Taaki
2012-06-16 6:45 ` Wladimir
2012-06-16 8:16 ` Andy Parkins
2012-06-16 8:42 ` Wladimir
2012-06-16 9:16 ` Amir Taaki
2012-06-16 9:54 ` Andy Parkins
2012-06-17 15:19 ` Jeff Garzik
2012-06-17 16:30 ` Amir Taaki
2012-06-18 1:27 ` Mark Friedenbach
2012-06-16 8:17 ` Andy Parkins
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='CA+8xBpdD31koaVBh1RuDZKH1sygr8z10K=bPz8DepqYOa8i6yg@mail.gmail.com' \
--to=jgarzik@exmulti.com \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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