From: Amir Taaki <zgenjix@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Proposed new P2P command and response: getcmds, cmdlist
Date: Fri, 15 Jun 2012 18:34:53 -0700 (PDT) [thread overview]
Message-ID: <1339810493.15660.YahooMailNeo@web121004.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CA+8xBpdD31koaVBh1RuDZKH1sygr8z10K=bPz8DepqYOa8i6yg@mail.gmail.com>
Introspection/command discovery is nice, but I would prefer it to be immediately done in the first version exchange so no assumptions as to how a network is operating need to be made.
I like the idea of a flat list of commands. It might make sense to have "meta"-commands that alias to groups of commands. i.e "original" for the current core subset up to (and including) "pong". The aliases could exist in a text definition file which is held on github or bitcoin.org/
----- Original Message -----
From: Jeff Garzik <jgarzik@exmulti•com>
To: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Cc:
Sent: Saturday, June 16, 2012 2:13 AM
Subject: [Bitcoin-development] Proposed new P2P command and response: getcmds, cmdlist
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
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists•sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
next prev parent reply other threads:[~2012-06-16 1:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 0:13 Jeff Garzik
2012-06-16 1:34 ` Amir Taaki [this message]
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=1339810493.15660.YahooMailNeo@web121004.mail.ne1.yahoo.com \
--to=zgenjix@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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