From: Chris Double <chris.double@double•co.nz>
To: "Rune Kjær Svendsen" <runesvend@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Implementing batch processing for -blocknotify
Date: Sat, 1 Jun 2013 10:20:05 +1200 [thread overview]
Message-ID: <CALn1vHG5VbT4BeFW89DCAx0fzkjaGpABEMEZO42pAs-wdi-e5Q@mail.gmail.com> (raw)
In-Reply-To: <CAH2=CKzW41TYbX6c1F8oknA_LttOaA8vmDPmojuowXgEADY61g@mail.gmail.com>
On Fri, May 31, 2013 at 11:56 PM, Rune Kjær 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.
--
http://www.bluishcoder.co.nz
next prev parent reply other threads:[~2013-05-31 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-31 11:56 Rune Kjær Svendsen
2013-05-31 12:10 ` Michael Hendricks
2013-05-31 12:37 ` Rune Kjær Svendsen
2013-05-31 19:25 ` Jeff Garzik
2013-05-31 12:54 ` Andy Parkins
2013-05-31 13:05 ` Jeff Garzik
2013-05-31 22:20 ` Chris Double [this message]
2013-05-31 23:29 ` Wladimir
2013-05-31 23:47 ` Chris Double
2013-06-01 13:12 ` Rune Kjær Svendsen
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=CALn1vHG5VbT4BeFW89DCAx0fzkjaGpABEMEZO42pAs-wdi-e5Q@mail.gmail.com \
--to=chris.double@double$(echo .)co.nz \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=runesvend@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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