I'd also like to be able to get detailed information of message format
errors for debugging other nodes that connect to bitcoind. For
instance, if a transaction is rejected because the signature is
invalid, I want to know this. If it's because the amount is out of
range or because the output
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
The callback architecture could be such that other code would never
need to enter into the wallet-handling process/memory space. For
instance, client applications could subscribe a particular URL to get
sent an HTTP POST.
For the apps I've been working on, there really isn't any need to
access
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
I spent some time changing the internal bitcoin code to use callback
hooks, but its far from complete (or even really usable from anything
other than the code in the satoshi client itself, it doesnt even have
any deregister methods!). As it sits now, it is likely to get more
eyeballs and merged
5 matches
Mail list logo
