From: Gregory Maxwell <gmaxwell@gmail•com>
To: Jeff Garzik <jgarzik@exmulti•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP: Custom Services
Date: Mon, 13 Aug 2012 11:07:55 -0400 [thread overview]
Message-ID: <CAAS2fgSgE0fOetuJZDPVeEMxbDo91r0w3Hvvn4vDdChCH1zxdA@mail.gmail.com> (raw)
In-Reply-To: <CA+8xBpfZzxBgqO6xT6+a_ACgYR=3cV9rmY_kmSovtT3dfjdhDg@mail.gmail.com>
On Mon, Aug 13, 2012 at 10:24 AM, Jeff Garzik <jgarzik@exmulti•com> wrote:
> My only response is a weak one: inevitability. It seems likely that
> -somebody- will implement their own P2P commands for their own client
> subset, even if only a simple "use 'getstatus' with strSubVer matching
> /FooClient/"
>
> Therefore, if it is inevitable, we might as well make some basic rules
> about how to extended your P2P command set.
I'm not opposed to that logic. But for cases where an introduction mechanism
will be needed... it would be awfully good to have one, and I do think that
there is harm in making people think that simple services negotiation will
actually work for their needs for cases where a separate p2p network is
needed.
prev parent reply other threads:[~2012-08-13 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-13 7:41 Stefan Thomas
2012-08-13 13:15 ` Mike Hearn
2012-08-13 20:00 ` Stefan Thomas
2012-08-13 14:24 ` Jeff Garzik
2012-08-13 15:07 ` Gregory Maxwell [this message]
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=CAAS2fgSgE0fOetuJZDPVeEMxbDo91r0w3Hvvn4vDdChCH1zxdA@mail.gmail.com \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jgarzik@exmulti$(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