mirror of
https://github.com/bisq-network/bisq.git
synced 2024-11-20 02:12:00 +01:00
Change order of tasks
Call BuyerSetupPayoutTxListener before BuyerSendCounterCurrencyTransferStartedMessage We will change BuyerSendCounterCurrencyTransferStartedMessage so that it does not complete until the message has been ACKed by the peer. It is more transparent to leave the task uncompleted and if it is the last task we dont have issues. The caller would not get the result handler called though until all is completed. But the result handler in the UI was anyway empty.
This commit is contained in:
parent
b13e1a3edb
commit
96221317e2
@ -234,8 +234,8 @@ public class BuyerAsMakerProtocol extends TradeProtocol implements BuyerProtocol
|
||||
MakerVerifyTakerAccount.class,
|
||||
MakerVerifyTakerFeePayment.class,
|
||||
BuyerSignPayoutTx.class,
|
||||
BuyerSendCounterCurrencyTransferStartedMessage.class,
|
||||
BuyerSetupPayoutTxListener.class
|
||||
BuyerSetupPayoutTxListener.class,
|
||||
BuyerSendCounterCurrencyTransferStartedMessage.class
|
||||
);
|
||||
taskRunner.run();
|
||||
} else {
|
||||
|
@ -198,7 +198,6 @@ public class BuyerAsTakerProtocol extends TradeProtocol implements BuyerProtocol
|
||||
taskRunner.run();
|
||||
}
|
||||
|
||||
|
||||
// The DepositTxAndDelayedPayoutTxMessage is a mailbox message as earlier we use only the deposit tx which can
|
||||
// be also received from the network once published.
|
||||
// Now we send the delayed payout tx as well and with that this message is mandatory for continuing the protocol.
|
||||
@ -263,8 +262,8 @@ public class BuyerAsTakerProtocol extends TradeProtocol implements BuyerProtocol
|
||||
TakerVerifyMakerAccount.class,
|
||||
TakerVerifyMakerFeePayment.class,
|
||||
BuyerSignPayoutTx.class,
|
||||
BuyerSendCounterCurrencyTransferStartedMessage.class,
|
||||
BuyerSetupPayoutTxListener.class
|
||||
BuyerSetupPayoutTxListener.class,
|
||||
BuyerSendCounterCurrencyTransferStartedMessage.class
|
||||
);
|
||||
taskRunner.run();
|
||||
} else {
|
||||
|
Loading…
Reference in New Issue
Block a user