From: "Michael Grønager" <gronager@ceptacle•com>
To: bitcoin-list@bluematt•me
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Adding callback hooks to the satoshi client
Date: Thu, 22 Mar 2012 10:56:00 +0100 [thread overview]
Message-ID: <7E6B77BA-6F88-4632-B9DD-487E870D45CA@ceptacle.com> (raw)
In-Reply-To: <15bcfa26-7be9-4883-ad03-bfb7085b5df0@email.android.com>
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
>
> 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
> http://p.sf.net/sfu/sfd2d-msazure
>
> 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
> 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/
next prev parent reply other threads:[~2012-03-22 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 5:13 Eric Lombrozo
2012-03-22 5:24 ` Matt Corallo
2012-03-22 5:39 ` bitcoin-list
2012-03-22 9:56 ` Michael Grønager [this message]
2012-03-22 14:00 ` Luke-Jr
2012-03-22 15:23 ` Eric Lombrozo
2012-03-24 8:41 ` Eric Lombrozo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7E6B77BA-6F88-4632-B9DD-487E870D45CA@ceptacle.com \
--to=gronager@ceptacle$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=bitcoin-list@bluematt$(echo .)me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox