From: Jeff Garzik <jgarzik@bitpay•com>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related services
Date: Fri, 8 Aug 2014 08:06:16 -0400 [thread overview]
Message-ID: <CAJHLa0PQYOOXoniDJFvb4Cy=-0cbh5bxWrYQO72mCAo-zXBJnQ@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJCbCRQP_w3g-0qtA6K8qrf6ywNfJ9d1367gSTfgCwgU2Q@mail.gmail.com>
On Fri, Aug 8, 2014 at 7:59 AM, Wladimir <laanwj@gmail•com> wrote:
> On Fri, Aug 8, 2014 at 1:38 PM, Mike Hearn <mike@plan99•net> wrote:
>> I'd like to see a mechanism whereby a Bitcoin node can delegate processing
>> of unknown messages to an external process, so a P2P node can be composed
>> out of separated programs, but such a service would be indistinguishable at
>> the network layer from one provided by Bitcoin Core itself, so a service bit
>> would be appropriate for those.
>
> This diverges from the topic but seems like a good idea to me in
> general, not so much as replacement for jgarzik's proposal.
>
> Something like `getutxos` or this proposal could be implemented as an
> external application or script, instead of having to integrate
> everything into bitcoind.
Seconded. Command plug-ins and such seem like an idea worth exploring.
We don't need to shove everything into bitcoind.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
next prev parent reply other threads:[~2014-08-08 12:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 3:38 Jeff Garzik
2014-08-08 9:45 ` Mike Hearn
2014-08-08 9:56 ` Wladimir
2014-08-08 10:01 ` Mike Hearn
2014-08-08 10:15 ` Wladimir
2014-08-08 10:26 ` Wladimir
2014-08-08 10:41 ` Christian Decker
2014-08-08 11:22 ` Jeff Garzik
2014-08-08 11:33 ` Jeff Garzik
2014-08-08 11:38 ` Mike Hearn
2014-08-08 11:59 ` Wladimir
2014-08-08 12:06 ` Jeff Garzik [this message]
2014-08-08 12:11 ` Jeff Garzik
2014-08-08 12:15 ` Wladimir
2014-08-08 12:11 ` Mike Hearn
2014-08-08 12:15 ` Jeff Garzik
2014-08-08 12:16 ` Wladimir
2014-08-08 12:34 ` Wladimir
2014-08-08 13:55 ` Mike Hearn
2014-08-08 12:04 ` Jeff Garzik
2014-08-08 12:13 ` Mike Hearn
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='CAJHLa0PQYOOXoniDJFvb4Cy=-0cbh5bxWrYQO72mCAo-zXBJnQ@mail.gmail.com' \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@gmail$(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