Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bluematt.me
	designates 173.246.101.161 as permitted sender)
	client-ip=173.246.101.161;
	envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; 
References: <CABr1YTc0TOvfyFNY4CTaOiTa3WWb-5JHjQOTarB=8zZ+DqiUFg@mail.gmail.com>
User-Agent: K-9 Mail for Android
In-Reply-To: <CABr1YTc0TOvfyFNY4CTaOiTa3WWb-5JHjQOTarB=8zZ+DqiUFg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----D6U7FSX4NLEVVEOBX7959YHDIHB728"
From: bitcoin-list@bluematt.me
Date: Thu, 22 Mar 2012 01:39:06 -0400
To: bitcoin-development@lists.sourceforge.net
Message-ID: <15bcfa26-7be9-4883-ad03-bfb7085b5df0@email.android.com>
Subject: Re: [Bitcoin-development] Adding callback hooks to the satoshi
	client
Precedence: list

------D6U7FSX4NLEVVEOBX7959YHDIHB728
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

You might also want to check out libcoin. Its a fork of the satoshi clien=
t: https://github.com/ceptacle/libcoin

Matt

Eric Lombrozo <elombrozo@gmail.com> wrote:

Hey, guys.

I've been writing a number of apps that require realtime event
notifications, where the JSON-RPC API clearly doesn't suffice.

There are two approaches I've been taking to this end:

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.

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.

I would like to propose adding these callback hooks to the main
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.

-Eric Lombrozo

_____________________________________________

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


------D6U7FSX4NLEVVEOBX7959YHDIHB728
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body>You might also want to check out libcoin.  Its a=
 fork of the satoshi client: <a href=3D"https://github.com/ceptacle/libco=
in">https://github.com/ceptacle/libcoin</a><br>
<br>
Matt<br><br><div class=3D"gmail_quote">Eric Lombrozo &lt;elombrozo@gmail.=
com&gt; wrote:<blockquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt =
0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"=
>
<pre style=3D"white-space: pre-wrap; word-wrap:break-word; font-family: s=
ans-serif">Hey, guys.<br /><br />I've been writing a number of apps that =
require realtime event<br />notifications, where the JSON-RPC API clearly=
 doesn't suffice.<br /><br />There are two approaches I've been taking to=
 this end:<br /><br />1) Writing my own library for dealing with raw bitc=
oin structures and<br />connecting to bitcoin nodes via the bitcoin proto=
col.<br />2) Making custom builds of the satoshi client putting callback =
hooks<br />in key points.<br /><br />Neither of these two approaches is i=
deal. (1) involves a lot of code<br />duplication, (2) involves patching =
the satoshi client source<br />each time I grab a later version, with the=
 everpresent risk of<br />something breaking and the need to continue mai=
ntaining these patches.<br />Moreover, unfortunately many of these key po=
ints happen to be in files<br />like main.cpp which see frequent changes.=
<br /><br />I would like to propose adding these
callback hooks to the main<br />branch. I am willing to help locate these=
 key points, reorganize the<br />code<br />to place these methods in sepa=
rate source files, define a callback<br />mechanism, and contribute sourc=
e code.<br /><br />-Eric Lombrozo<br /><br /><hr /><br />This SF email is=
 sponsosred by:<br />Try Windows Azure free for 90 days Click Here <br />=
<a href=3D"http://p.sf.net/sfu/sfd2d-msazure">http://p.sf.net/sfu/sfd2d-m=
sazure</a><br /><hr /><br />Bitcoin-development mailing list<br />Bitcoin=
-development@lists.sourceforge.net<br /><a href=3D"https://lists.sourcefo=
rge.net/lists/listinfo/bitcoin-development">https://lists.sourceforge.net=
/lists/listinfo/bitcoin-development</a><br /></pre></blockquote></div></b=
ody></html>
------D6U7FSX4NLEVVEOBX7959YHDIHB728--