From: "Luke-Jr" <luke@dashjr•org>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Adding callback hooks to the satoshi client
Date: Thu, 22 Mar 2012 10:00:40 -0400 [thread overview]
Message-ID: <201203221000.41636.luke@dashjr.org> (raw)
In-Reply-To: <CABr1YTc0TOvfyFNY4CTaOiTa3WWb-5JHjQOTarB=8zZ+DqiUFg@mail.gmail.com>
On Thursday, March 22, 2012 1:13:13 AM Eric Lombrozo wrote:
> 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.
I'm not sure it's a good idea to let other code into the main wallet-handling
process/memory space. I'd suggest looking into designing a workable Wallet
Protocol for general use between the wallet and GUIs/applications.
https://en.bitcoin.it/wiki/Wallet_protocol has a draft I made a long time ago,
but really seems a bit overcomplicated.
next prev parent reply other threads:[~2012-03-22 14:01 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
2012-03-22 14:00 ` Luke-Jr [this message]
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=201203221000.41636.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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