This lists the capabilities of the remote node, in the form of a vector<string> list of commands advertised by remote node.
Add new P2P command and response: "getcmds", "cmdlist" #1471
pull jgarzik wants to merge 1 commits into bitcoin:master from jgarzik:list-ops changing 1 files +30 −0-
jgarzik commented at 12:08 AM on June 16, 2012: contributor
-
aa412d4e18
Add new P2P command and response: "getcmds", "cmdlist"
This lists the capabilities of the remote node, in the form of a vector<string> list of commands advertised by remote node.
-
laanwj commented at 6:38 AM on June 16, 2012: member
What's up with adding all the P2P commands lately? Shouldn't this be discussed in a BIP?
Personally I still think it's better to have a clear standardized "protocol version", that implies what capabilities are supported, instead of a capability-based system that explicitly lists them.
Capability-based systems tend to become horrendously complex, as you have to take into account all possible combinations of possible interactions, and constantly check for support of specific features instead of just comparing a version number.
-
-
jgarzik commented at 12:54 PM on June 16, 2012: contributor
No, you don't discuss things in a BIP. You first implement the code, then discuss on the mailing list and forums.
-
laanwj commented at 1:38 PM on June 16, 2012: member
Yes I meant describe in a BIP.
-
luke-jr commented at 10:00 PM on June 18, 2012: member
@jgarzik Well, FWIW, @gavinandresen is always saying to discuss on the mailing list before making pull requests...
But this whole thread of discussion is IMO off-topic for here...
-
jgarzik commented at 3:52 PM on June 27, 2012: contributor
Closing, not sufficient consensus or interest, based on mailing list discussion
- jgarzik closed this on Jun 27, 2012
- jgarzik deleted the branch on Aug 24, 2014
- lateminer referenced this in commit 617fd9998c on Jan 22, 2019
- lateminer referenced this in commit 7fdf25b4f7 on May 6, 2020
- DrahtBot locked this on Sep 8, 2021
