回复：JSON-RPC 方法构想：列出比给定 txid 更新的交易
原始发布页
打开来源页面查看 1 个交叉存档
引用自：jgarzik，2010 年 12 月 09 日上午 12:58:05
关于“<txid> 之后的交易”，我同意你和 satoshi 的看法。我的 listtransactions（现在是 xlisttransactions）补丁明确没有这个功能，而且从来没有过。
只要这个接口是为向用户显示最近 N 笔交易历史之类的用途而设计，就没问题；现在我们有了账户功能，也更容易以正确方式进行付款检测。
Gavin，listtransactions 能否提供一个选项，列出所有账户的交易？
我不确定接口可以设计成什么样，也许是： listtransactions <JSON null type> [count]
不过，从命令行这样操作会很困难。
我想不出一个好的接口方案，这正是问题所在。也许像 "" 那样，把 "*" 作为特殊情况。所有人都必须确保用户不能创建名为 "*" 的账户。
引用自：jgarzik，2010 年 12 月 09 日下午 04:13:50
当然，而且通过交易很容易追踪。
我不明白怎么会“容易”通过交易追踪。
英文原文
展开英文原文
Quote from: jgarzik on December 09, 2010, 12:58:05 AM
I agree with you and satoshi about "txs after <txid>". My listtransactions (now xlisttransactions) patch pointedly does not have that feature, and never has.
As long as the interface is designed for things like showing the user the last N transactions history, it's fine, now that we have the Accounts feature making it easier to do payment detection the right way.
Gavin, could listtransactions have an option to list transactions for all accounts?
I'm not sure what the interface could be, maybe: listtransactions <JSON null type> [count]
It would be hard to do that from the command line though.
I can't think of a good solution for the interface, that's the problem. Maybe "*" special case like "" is. Everyone would have to make sure no user can create account name "*".
Quote from: jgarzik on December 09, 2010, 04:13:50 PM
Sure, and that's easy enough to track with transactions.
I don't get how that's "easy" to track with transactions.