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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <chris.double@gmail.com>) id 1UiXgr-0002DO-Mt
for bitcoin-development@lists.sourceforge.net;
Fri, 31 May 2013 22:20:53 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.43 as permitted sender)
client-ip=209.85.220.43; envelope-from=chris.double@gmail.com;
helo=mail-pa0-f43.google.com;
Received: from mail-pa0-f43.google.com ([209.85.220.43])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UiXgq-0005N3-0q
for bitcoin-development@lists.sourceforge.net;
Fri, 31 May 2013 22:20:53 +0000
Received: by mail-pa0-f43.google.com with SMTP id hz10so254004pad.30
for <bitcoin-development@lists.sourceforge.net>;
Fri, 31 May 2013 15:20:46 -0700 (PDT)
X-Received: by 10.66.231.7 with SMTP id tc7mr15367233pac.143.1370038846016;
Fri, 31 May 2013 15:20:46 -0700 (PDT)
MIME-Version: 1.0
Sender: chris.double@gmail.com
Received: by 10.70.118.162 with HTTP; Fri, 31 May 2013 15:20:05 -0700 (PDT)
In-Reply-To: <CAH2=CKzW41TYbX6c1F8oknA_LttOaA8vmDPmojuowXgEADY61g@mail.gmail.com>
References: <CAH2=CKzW41TYbX6c1F8oknA_LttOaA8vmDPmojuowXgEADY61g@mail.gmail.com>
From: Chris Double <chris.double@double.co.nz>
Date: Sat, 1 Jun 2013 10:20:05 +1200
X-Google-Sender-Auth: 4cM3AQPgBrcn9HIoc_eIHRu0PX4
Message-ID: <CALn1vHG5VbT4BeFW89DCAx0fzkjaGpABEMEZO42pAs-wdi-e5Q@mail.gmail.com>
To: =?ISO-8859-1?Q?Rune_Kj=E6r_Svendsen?= <runesvend@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -1.5 (-)
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
(chris.double[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
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: 1UiXgq-0005N3-0q
Cc: bitcoin-development@lists.sourceforge.net
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: Fri, 31 May 2013 22:20:53 -0000
On Fri, May 31, 2013 at 11:56 PM, Rune Kj=E6r Svendsen
<runesvend@gmail.com> wrote:
> I'm not quite so how to go about this.
As others have said, queuing outside of bitcoind is a better approach.
I use zeromq for this situation. blocknotify runs a program which uses
zeromq's pub/sub to queue and the application subscribes to this to
get notified of the data.
--=20
http://www.bluishcoder.co.nz
|
