1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1XFj1D-00045P-MP
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Aug 2014 12:11:35 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.213.176 as permitted sender)
client-ip=209.85.213.176; envelope-from=jgarzik@bitpay.com;
helo=mail-ig0-f176.google.com;
Received: from mail-ig0-f176.google.com ([209.85.213.176])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XFj1C-0007C1-QJ
for bitcoin-development@lists.sourceforge.net;
Fri, 08 Aug 2014 12:11:35 +0000
Received: by mail-ig0-f176.google.com with SMTP id hn18so907063igb.3
for <bitcoin-development@lists.sourceforge.net>;
Fri, 08 Aug 2014 05:11:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=KLFpN8YrcWhMAyy7ZetBUjCxDx403Om8wG0jt6RmUdQ=;
b=m8SM7vn8v3TEWS18ejYc7KCoxZ54LhFn/Ikm1O3Elv3dUbYWPuZC8HFArl4xid4Zb7
xWjOXBqdc5/o5r9Hh+pDN9fhLdf7pQMp1drIl+koASdOENt9YxckWoDeeK7hpFnIp8Pj
l4YcqqKXK+m5lZIbUcll8CpdnrlO/94v51/mDFxbO2KFbGqdnlDRsdBVOcmCpW4YRd6a
qprhMmL2SzkfKeky4ErYEf6p1+yKuwCKQcF4XWheLVSidG8vIuInbCN4AGt77XihGumW
9miO7zqrtj/32QEjQYzfoCzhV575IV99JTzVZhRHjPlcJVPgSHFrJYcCF04u6CYOgfUd
v76A==
X-Gm-Message-State: ALoCoQlMVs21AY0wtvPW7Nht0mAhZJp1+wOXG069Fj4i+5Qb4eSfuhuwH+1HV4e82O45vizu+O+0
X-Received: by 10.42.214.207 with SMTP id hb15mr11576712icb.30.1407499889350;
Fri, 08 Aug 2014 05:11:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.10.78 with HTTP; Fri, 8 Aug 2014 05:11:08 -0700 (PDT)
In-Reply-To: <CA+s+GJCbCRQP_w3g-0qtA6K8qrf6ywNfJ9d1367gSTfgCwgU2Q@mail.gmail.com>
References: <CAJHLa0Ok6s5xQcMSeLa69adLBXEaicuXqcg45eZrwYtVFbx-dA@mail.gmail.com>
<CANEZrP2wYcxJhxRRa86Nm9ENtK2SA5VNG-L7f5pHb_W=Ajcj5Q@mail.gmail.com>
<CA+s+GJD+9qpwFcVfHOCCsFYjmk7A0V=65vG-7jJ6D7jj4Pi_7g@mail.gmail.com>
<CANEZrP245242JYDBBo72XVmKgEBO96QPjcJi8Jy2Dm_r90n1Bw@mail.gmail.com>
<CAJHLa0N3xx1QZ==iSLYNsdgkBGoqN34+4eVtukkjn+3SrDhC7A@mail.gmail.com>
<CANEZrP1mhSodC-ZvkuVKAgHO44bM7QX=RivRDhnDeHOKr8PXqQ@mail.gmail.com>
<CA+s+GJCbCRQP_w3g-0qtA6K8qrf6ywNfJ9d1367gSTfgCwgU2Q@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 8 Aug 2014 08:11:08 -0400
Message-ID: <CAJHLa0NQJCH_J6wOLHKyyG4au4WT7Dviz-xXc33XkZEaYCaBuQ@mail.gmail.com>
To: Wladimir <laanwj@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1XFj1C-0007C1-QJ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related
services
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 08 Aug 2014 12:11:35 -0000
On Fri, Aug 8, 2014 at 7:59 AM, Wladimir <laanwj@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/
|
