public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Chris Double <chris.double@double.co.nz>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Implementing batch processing for -blocknotify
Date: Sat, 1 Jun 2013 11:47:17 +1200	[thread overview]
Message-ID: <CALn1vHGFWSbKDhm0_hkJOoZzMGicERJ9=1uHUqFhOyw8xMNqgA@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJBo18mC84=09vEYZ0n7WVeA0MV2OfdvFDap0_sW7TinyA@mail.gmail.com>

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



  reply	other threads:[~2013-05-31 23:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31 11:56 [Bitcoin-development] Implementing batch processing for -blocknotify 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
2013-05-31 23:29   ` Wladimir
2013-05-31 23:47     ` Chris Double [this message]
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='CALn1vHGFWSbKDhm0_hkJOoZzMGicERJ9=1uHUqFhOyw8xMNqgA@mail.gmail.com' \
    --to=chris.double@double.co.nz \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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