On Wednesday, May 16, 2012 6:18:27 PM Jeff Garzik wrote: > Instead of further overloading service bits in the version message, or > altering the version message, let us instead make feature discovery an > easy, flexible, extensible process. > > We can add new commands without impacting older nodes, so let's create > a new command "get-features" (or pick your name) that returns a list > of key/value pairs. The key is a string, the value type is determined > by the key.
That assumes you already have a connection to the peer in question. As I understand it, the service bits are propagated as part of the address, so you can see at a glance which nodes you want to connect to for some special service. Passing a huge list along might be unwieldy (though it makes sense for protocol changes that don't add new services). ------------------------------------------------------------------------------ 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
