From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) id 1UiZ3F-0005gQ-2s for bitcoin-development@lists.sourceforge.net; Fri, 31 May 2013 23:48:05 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.44 as permitted sender) client-ip=209.85.160.44; envelope-from=chris.double@gmail.com; helo=mail-pb0-f44.google.com; Received: from mail-pb0-f44.google.com ([209.85.160.44]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UiZ3D-0001oh-PH for bitcoin-development@lists.sourceforge.net; Fri, 31 May 2013 23:48:05 +0000 Received: by mail-pb0-f44.google.com with SMTP id wz12so2990671pbc.17 for ; Fri, 31 May 2013 16:47:58 -0700 (PDT) X-Received: by 10.66.145.229 with SMTP id sx5mr15771292pab.11.1370044077959; Fri, 31 May 2013 16:47:57 -0700 (PDT) MIME-Version: 1.0 Sender: chris.double@gmail.com Received: by 10.70.118.162 with HTTP; Fri, 31 May 2013 16:47:17 -0700 (PDT) In-Reply-To: References: From: Chris Double Date: Sat, 1 Jun 2013 11:47:17 +1200 X-Google-Sender-Auth: lKh5JKdxK0hqOBr4xVPT5VvE-c8 Message-ID: To: Bitcoin Dev Content-Type: text/plain; charset=ISO-8859-1 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: 1UiZ3D-0001oh-PH 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 May 2013 23:48:05 -0000 On Sat, Jun 1, 2013 at 11:29 AM, Wladimir 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