public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.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 14:15:09 +0200	[thread overview]
Message-ID: <CA+s+GJCdnHeSRWnmiBG+JHJDUwKRpKfaSDwu24kMp9WEQCNa1A@mail.gmail.com> (raw)
In-Reply-To: <CAJHLa0NQJCH_J6wOLHKyyG4au4WT7Dviz-xXc33XkZEaYCaBuQ@mail.gmail.com>

> 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.

ZeroMQ is just a lightweight message routing system. It could just as
well make P2P messages available to other applications (if they
subscribe to them). The other way around, routing messages from ZeroMQ
to certain P2P clients, is easy.

Wladimir



  reply	other threads:[~2014-08-08 12:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  3:38 [Bitcoin-development] NODE_EXT_SERVICES and advertising related services 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
2014-08-08 12:11             ` Jeff Garzik
2014-08-08 12:15               ` Wladimir [this message]
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=CA+s+GJCdnHeSRWnmiBG+JHJDUwKRpKfaSDwu24kMp9WEQCNa1A@mail.gmail.com \
    --to=laanwj@gmail.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=jgarzik@bitpay.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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