Qortal/altcoinj
3
0
Fork 0
mirror of https://github.com/Qortal/altcoinj.git synced 2025-02-12 10:15:52 +00:00
Code Issues Projects Releases Wiki Activity

WalletEventListener: Remove obsolete references to being called on Peer threads from the javadocs.

Browse Source
This commit is contained in:
Mike Hearn 2013-07-29 17:18:21 +02:00
parent da2a321c23
commit 872967e96e
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
core/src/main/java/com/google/bitcoin/core/WalletEventListener.java
View File

@ -25,7 +25,7 @@ import java.util.List;
*/ */
public interface WalletEventListener { public interface WalletEventListener {
/** /**
* This is called on a Peer thread when a transaction is seen that sends coins <b>to</b> this wallet, either because it * This is called when a transaction is seen that sends coins <b>to</b> this wallet, either because it
* was broadcast across the network or because a block was received. If a transaction is seen when it was broadcast, * was broadcast across the network or because a block was received. If a transaction is seen when it was broadcast,
* onCoinsReceived won't be called again when a block containing it is received. If you want to know when such a * onCoinsReceived won't be called again when a block containing it is received. If you want to know when such a
* transaction receives its first confirmation, register a {@link TransactionConfidence} event listener using * transaction receives its first confirmation, register a {@link TransactionConfidence} event listener using
@ -40,7 +40,7 @@ public interface WalletEventListener {
void onCoinsReceived(Wallet wallet, Transaction tx, BigInteger prevBalance, BigInteger newBalance); void onCoinsReceived(Wallet wallet, Transaction tx, BigInteger prevBalance, BigInteger newBalance);
/** /**
* This is called on a Peer thread when a transaction is seen that sends coins <b>from</b> this wallet, either * This is called when a transaction is seen that sends coins <b>from</b> this wallet, either
* because it was broadcast across the network or because a block was received. This may at first glance seem * because it was broadcast across the network or because a block was received. This may at first glance seem
* useless, because in the common case you already know about such transactions because you created them with * useless, because in the common case you already know about such transactions because you created them with
* the Wallets createSend/sendCoins methods. However when you have a wallet containing only keys, and you wish * the Wallets createSend/sendCoins methods. However when you have a wallet containing only keys, and you wish
@ -59,8 +59,8 @@ public interface WalletEventListener {
// TODO: Finish onReorganize to be more useful. // TODO: Finish onReorganize to be more useful.
/** /**
* <p>This is called on a Peer thread when a block is received that triggers a block chain re-organization. * <p>This is called when a block is received that triggers a block chain re-organization.</p>
* </p> *
* <p>A re-organize means that the consensus (chain) of the network has diverged and now changed from what we * <p>A re-organize means that the consensus (chain) of the network has diverged and now changed from what we
* believed it was previously. Usually this won't matter because the new consensus will include all our old * believed it was previously. Usually this won't matter because the new consensus will include all our old
* transactions assuming we are playing by the rules. However it's theoretically possible for our balance to * transactions assuming we are playing by the rules. However it's theoretically possible for our balance to
@ -71,7 +71,7 @@ public interface WalletEventListener {
void onReorganize(Wallet wallet); void onReorganize(Wallet wallet);
/** /**
* <p>Called on a Peer thread when a transaction changes its confidence level. You can also attach event listeners to * <p>Called when a transaction changes its confidence level. You can also attach event listeners to
* the individual transactions, if you don't care about all of them. Usually you would save the wallet to disk after * the individual transactions, if you don't care about all of them. Usually you would save the wallet to disk after
* receiving this callback unless you already set up autosaving.</p> * receiving this callback unless you already set up autosaving.</p>
* *