1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gronager@ceptacle.com>) id 1SAekf-0005kd-PR
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Mar 2012 09:56:13 +0000
X-ACL-Warn:
Received: from 2508ds5-oebr.0.fullrate.dk ([95.166.54.49]
helo=mail.ceptacle.com)
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1SAekZ-0004cY-TD for bitcoin-development@lists.sourceforge.net;
Thu, 22 Mar 2012 09:56:13 +0000
Received: from localhost (localhost [127.0.0.1])
by mail.ceptacle.com (Postfix) with ESMTP id C89E3197681A;
Thu, 22 Mar 2012 10:56:01 +0100 (CET)
X-Virus-Scanned: amavisd-new at ceptacle.com
Received: from mail.ceptacle.com ([127.0.0.1])
by localhost (server.ceptacle.private [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id LJvDddFjdbGk; Thu, 22 Mar 2012 10:56:01 +0100 (CET)
Received: from [109.105.106.219] (unknown [109.105.106.219])
by mail.ceptacle.com (Postfix) with ESMTPSA id 8CB2E1976814;
Thu, 22 Mar 2012 10:56:01 +0100 (CET)
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
X-Mailer: Apple Mail (2.1257)
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1SAekZ-0004cY-TD
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Adding callback hooks to the
satoshi client
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2012 09:56:13 -0000
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/
|
