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
134
135
136
137
138
139
140
141
142
143
144
145
146
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin-list@bluematt.me>) id 1SAak3-0002QM-0w
for bitcoin-development@lists.sourceforge.net;
Thu, 22 Mar 2012 05:39:19 +0000
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;
Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me)
by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1SAak1-0005J4-PY for bitcoin-development@lists.sourceforge.net;
Thu, 22 Mar 2012 05:39:19 +0000
Received: from [21.83.89.158] (66-87-109-158.pools.spcsdns.net [66.87.109.158])
by mail.bluematt.me (Postfix) with ESMTPSA id 7511E317C
for <bitcoin-development@lists.sourceforge.net>;
Thu, 22 Mar 2012 05:36:38 +0000 (UTC)
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>
X-Spam-Score: -0.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 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1SAak1-0005J4-PY
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 05:39:19 -0000
------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 <elombrozo@gmail.=
com> 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--
|
