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
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <runesvend@gmail.com>) id 1UilcB-0001xS-DY
for bitcoin-development@lists.sourceforge.net;
Sat, 01 Jun 2013 13:12:59 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.42 as permitted sender)
client-ip=74.125.82.42; envelope-from=runesvend@gmail.com;
helo=mail-wg0-f42.google.com;
Received: from mail-wg0-f42.google.com ([74.125.82.42])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UilcA-0006zF-D2
for bitcoin-development@lists.sourceforge.net;
Sat, 01 Jun 2013 13:12:59 +0000
Received: by mail-wg0-f42.google.com with SMTP id n12so1459313wgh.1
for <bitcoin-development@lists.sourceforge.net>;
Sat, 01 Jun 2013 06:12:52 -0700 (PDT)
X-Received: by 10.194.95.167 with SMTP id dl7mr12994426wjb.46.1370092372205;
Sat, 01 Jun 2013 06:12:52 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.161.227 with HTTP; Sat, 1 Jun 2013 06:12:32 -0700 (PDT)
In-Reply-To: <CALn1vHGFWSbKDhm0_hkJOoZzMGicERJ9=1uHUqFhOyw8xMNqgA@mail.gmail.com>
References: <CAH2=CKzW41TYbX6c1F8oknA_LttOaA8vmDPmojuowXgEADY61g@mail.gmail.com>
<CALn1vHG5VbT4BeFW89DCAx0fzkjaGpABEMEZO42pAs-wdi-e5Q@mail.gmail.com>
<CA+s+GJBo18mC84=09vEYZ0n7WVeA0MV2OfdvFDap0_sW7TinyA@mail.gmail.com>
<CALn1vHGFWSbKDhm0_hkJOoZzMGicERJ9=1uHUqFhOyw8xMNqgA@mail.gmail.com>
From: =?ISO-8859-1?Q?Rune_Kj=E6r_Svendsen?= <runesvend@gmail.com>
Date: Sat, 1 Jun 2013 15:12:32 +0200
Message-ID: <CAH2=CKy5=s3MvNMS6gLj2HZG-5EW5buy5odcnYYf0rZa84t+TQ@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7bb042f227a65304de177d99
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(runesvend[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1UilcA-0006zF-D2
Subject: Re: [Bitcoin-development] Implementing batch processing for
-blocknotify
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: Sat, 01 Jun 2013 13:12:59 -0000
--047d7bb042f227a65304de177d99
Content-Type: text/plain; charset=ISO-8859-1
Thanks for the input all! You make a lot of sense :). I will go with the
Unix socket method, I think. It's about time I learn about those.
/Rune
On Sat, Jun 1, 2013 at 1:47 AM, Chris Double <chris.double@double.co.nz>wrote:
> On Sat, Jun 1, 2013 at 11:29 AM, Wladimir <laanwj@gmail.com> wrote:
> > Using zmq is a great fit for high-speed notifications such as this. Have
> you
> > seen the pull request to integrate zmq directly into bitcoind, so that
> you
> > don't even need -blocknotify?
> >
> > https://github.com/bitcoin/bitcoin/pull/2415
> >
> > If not: we could use some testing there!
>
> I hadn't seen this, thanks! I've integrated zmq myself for block
> notifications in bitcoin and the alt coins I use it on my bitparking
> merge mining pool. I would love to see something official. I'll try
> out the patch in the pull request.
>
> Chris.
> --
> http://www.bluishcoder.co.nz
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--047d7bb042f227a65304de177d99
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Thanks for the input all! You make a lot of sense :). I wi=
ll go with the Unix socket method, I think. It's about time I learn abo=
ut those.<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">/R=
une<br>
<br><br><div class=3D"gmail_quote">On Sat, Jun 1, 2013 at 1:47 AM, Chris Do=
uble <span dir=3D"ltr"><<a href=3D"mailto:chris.double@double.co.nz" tar=
get=3D"_blank">chris.double@double.co.nz</a>></span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">
<div>On Sat, Jun 1, 2013 at 11:29 AM, Wladimir <<a href=3D"mailto:laanwj=
@gmail.com" target=3D"_blank">laanwj@gmail.com</a>> wrote:<br>
> Using zmq is a great fit for high-speed notifications such as this. Ha=
ve you<br>
> seen the pull request to integrate zmq directly into bitcoind, so that=
you<br>
> don't even need -blocknotify?<br>
><br>
> <a href=3D"https://github.com/bitcoin/bitcoin/pull/2415" target=3D"_bl=
ank">https://github.com/bitcoin/bitcoin/pull/2415</a><br>
><br>
> If not: we could use some testing there!<br>
<br>
</div>I hadn't seen this, thanks! I've integrated zmq myself for bl=
ock<br>
notifications in bitcoin and the alt coins I use it on my bitparking<br>
merge mining pool. I would love to see something official. I'll try<br>
out the patch in the pull request.<br>
<span><font color=3D"#888888"><br>
Chris.<br>
</font></span><div><div>--<br>
<a href=3D"http://www.bluishcoder.co.nz" target=3D"_blank">http://www.bluis=
hcoder.co.nz</a><br>
<br>
---------------------------------------------------------------------------=
---<br>
Get 100% visibility into Java/.NET code with AppDynamics Lite<br>
It's a free troubleshooting tool designed for production<br>
Get down to code-level detail for bottlenecks, with <2% overhead.<br>
Download for free and get started troubleshooting in minutes.<br>
<a href=3D"http://p.sf.net/sfu/appdyn_d2d_ap2" target=3D"_blank">http://p.s=
f.net/sfu/appdyn_d2d_ap2</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br></div></div>
--047d7bb042f227a65304de177d99--
|
