Mime-Version: 1.0 (Apple Message framework v1257)
Content-Type: text/plain; charset=us-ascii
From: =?iso-8859-1?Q?Michael_Gr=F8nager?= <gronager@ceptacle.com>
In-Reply-To: <15bcfa26-7be9-4883-ad03-bfb7085b5df0@email.android.com>
Date: Thu, 22 Mar 2012 10:56:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E6B77BA-6F88-4632-B9DD-487E870D45CA@ceptacle.com>
References: <CABr1YTc0TOvfyFNY4CTaOiTa3WWb-5JHjQOTarB=8zZ+DqiUFg@mail.gmail.com>
	<15bcfa26-7be9-4883-ad03-bfb7085b5df0@email.android.com>
To: bitcoin-list@bluematt.me
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Adding callback hooks to the
	satoshi	client
Precedence: list

Hi Eric,

What hooks are you looking for in particular ?

libcoin supports registration of listeners for new blocks and new =
transactions. These are e.g. used for connecting the Wallet to the Node.

Cheers,

M


On 22/03/2012, at 06:39, bitcoin-list@bluematt.me wrote:

> You might also want to check out libcoin. Its a fork of the satoshi =
client: https://github.com/ceptacle/libcoin
>=20
> Matt
>=20
> Eric Lombrozo <elombrozo@gmail.com> wrote:
> Hey, guys.
>=20
> I've been writing a number of apps that require realtime event
> notifications, where the JSON-RPC API clearly doesn't suffice.
>=20
> There are two approaches I've been taking to this end:
>=20
> 1) Writing my own library for dealing with raw bitcoin structures and
> connecting to bitcoin nodes via the bitcoin protocol.
> 2) Making custom builds of the satoshi client putting callback hooks
> in key points.
>=20
> Neither of these two approaches is ideal. (1) involves a lot of code
> duplication, (2) involves patching the satoshi client source
> each time I grab a later version, with the everpresent risk of
> something breaking and the need to continue maintaining these patches.
> Moreover, unfortunately many of these key points happen to be in files
> like main.cpp which see frequent changes.
>=20
> I would like to propose adding these
> callback hooks to the main
>=20
> branch. I am willing to help locate these key points, reorganize the
> code
> to place these methods in separate source files, define a callback
> mechanism, and contribute source code.
>=20
> -Eric Lombrozo
>=20
>=20
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here=20
> http://p.sf.net/sfu/sfd2d-msazure
>=20
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
> =
--------------------------------------------------------------------------=
----
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here=20
> =
http://p.sf.net/sfu/sfd2d-msazure_________________________________________=
______
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

Michael Gronager, PhD
Director, Ceptacle
Jens Juels Gade 33
2100 Copenhagen E
Mobile: +45 31 45 14 01
E-mail: gronager@ceptacle.com
Web: http://www.ceptacle.com/