Jeff Garzik [ARCHIVE] on Nostr: 📅 Original date posted:2014-08-08 📝 Original message:On Fri, Aug 8, 2014 at ...
📅 Original date posted:2014-08-08
📝 Original message:On Fri, Aug 8, 2014 at 7:59 AM, Wladimir <laanwj at gmail.com> wrote:
> Bitcoind would need a local interprocess message bus for that, and
> would need to act as router for messages from/to the P2P network.
> ZeroMQ seems like a good choice for that. That's not completely crazy
> as there are already plans to add zeromq as an optional dependency for
> notifications [1].
Generally agreed, though for ZMQ it is a bit different than a P2P service.
IMO, ZMQ really wants to be a plug-in that registers some internal
signals. It wants to capture the precise points where a block was
accepted internally. PR #4599 tries to lead by example:
https://github.com/bitcoin/bitcoin/pull/4599
A P2P service would be a slightly different sort of plug-in.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
📝 Original message:On Fri, Aug 8, 2014 at 7:59 AM, Wladimir <laanwj at gmail.com> wrote:
> Bitcoind would need a local interprocess message bus for that, and
> would need to act as router for messages from/to the P2P network.
> ZeroMQ seems like a good choice for that. That's not completely crazy
> as there are already plans to add zeromq as an optional dependency for
> notifications [1].
Generally agreed, though for ZMQ it is a bit different than a P2P service.
IMO, ZMQ really wants to be a plug-in that registers some internal
signals. It wants to capture the precise points where a block was
accepted internally. PR #4599 tries to lead by example:
https://github.com/bitcoin/bitcoin/pull/4599
A P2P service would be a slightly different sort of plug-in.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/