From: Amir Taaki <zgenjix@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] [RFC] listtransactions reformatting
Date: Sun, 17 Jul 2011 04:53:05 -0700 (PDT) [thread overview]
Message-ID: <1310903585.65859.YahooMailNeo@web121007.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CABsx9T2qhLiYAQNOCigXOMySgVqDqqQMotqYQwSPZEwkSYbY=g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2583 bytes --]
Oops, sorry Gavin. Meant to reply to the mailing list.
---------------
People should not be using accounts for receiving funds on
merchant sites. There are too many bugs associated with it, and it has
innumerable problems. Like not being able to merge wallets or lack of
find grained control when moving funds around.
https://gitorious.org/intersango/bitcoind/commit/50a6ab79ed8c5398648c52fbdc4be07f70dedadb
This is the recommended & most safest way to receive funds on a merchant site ATM.
listreceivedsince <timest> is called every so often by a cron job.
The output is parsed and placed into another table and then another job
will go and create a deposit request from that table. The next call to listreceivedsince <timest> will call with the time of the last
transaction, and doubles must be discarded using the txid.
Polling listtransactions is less convenient since you always repeat old
transactions that you may not need, get generated transactions and have
to pick a good number that goes back far enough, but not too far.
________________________________
From: Gavin Andresen <gavinandresen@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Sent: Sunday, July 17, 2011 5:02 AM
Subject: Re: [Bitcoin-development] [RFC] listtransactions reformatting
Fixing listtransactions (and listreceivedby/etc) so coin generation
transactions to particular addresses/accounts are credited to that
address/account is a good idea.
I don't think changing listtransactions output would be on the
priority list for any web services operators (in fact, I think most
would scream bloody murder if the output changed in a way that forced
them to change their code). The accounts-related things that I think
ARE on their high-priority list are:
1) Fixing getbalance and listtransactions performance problems when
you have hundreds of thousands of transactions and thousands of
accounts.
2) push-notification of coins received to accounts, so they don't have
to poll for changes.
--
--
Gavin Andresen
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Bitcoin-development mailing list
Bitcoin-development@lists•sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development
[-- Attachment #2: Type: text/html, Size: 3866 bytes --]
prev parent reply other threads:[~2011-07-17 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-16 17:14 Luke-Jr
2011-07-16 19:59 ` Stéphane Gimenez
2011-07-16 20:03 ` Luke-Jr
2011-07-17 3:02 ` Gavin Andresen
2011-07-17 11:53 ` Amir Taaki [this message]
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=1310903585.65859.YahooMailNeo@web121007.mail.ne1.yahoo.com \
--to=zgenjix@yahoo$(echo .)com \
--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