Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.210.46 as permitted sender)
	client-ip=209.85.210.46; envelope-from=gavinandresen@gmail.com;
	helo=mail-pz0-f46.google.com; 
MIME-Version: 1.0
In-Reply-To: <201107161603.08960.luke@dashjr.org>
References: <201107161314.13267.luke@dashjr.org>
	<20110716195907.GA311029@tenebreuse>
	<201107161603.08960.luke@dashjr.org>
Date: Sun, 17 Jul 2011 13:02:51 +1000
Message-ID: <CABsx9T2qhLiYAQNOCigXOMySgVqDqqQMotqYQwSPZEwkSYbY=g@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [Bitcoin-development] [RFC] listtransactions reformatting
Precedence: list

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