5 Commits (af0c7c5df81053b52ab41f8c2a2ec6cbb5b6ee1b)

Author	SHA1	Message	Date
wowario	af0c7c5df8	wowify	3 years ago
Daniel Karzel	dc89a837e7	Do not actively set `KeepAlice::No` for `swap_setup` ... Closing the connection upon completing the `swap_setup` protocol caused problems on the ASB side, because the CLI would close the connection before the last message was properly processed. This would result in swaps going into execution on the CLI side, but not on the ASB side. The CLI ensures an open connection to the ASB over the complete course of a swap. So it does not make much sense to allow a protocol to close the connection (the CLI would immediately redial). For the Alice we set the initial `KeepAlive` to `10` seconds because Bob is expected to request a spot price in reasonable time after opening a connection on the protocol. Since Tor connections can take some time we set 10 seconds fow now for resilience.	3 years ago
Daniel Karzel	cd14e22cdf	Longer timeout (120 secs) for `swap_setup` protocol ... Given that we combined the `spot_price` and the `execution_setup` messaging into one protocol we should allow the protocol to take longer than 60 seconds to complete. This is especially important for connections over Tor, where messaging can take significantly longer than over clearnet. I ran some tests with Tor and did not run into issues with the 60 seconds, but we get very close to the timeout, so we better make it more resilient by adding more time.	3 years ago
Daniel Karzel	fd18a07426	Flush and close `swap_setup` substreams ... When swapping on testnet we ran into a problem where the CLI started the swap after sending all messages successfully, but the ASB ran into a `connection closed` error at the end of the `swap_setup` and the swap state machine was never actually triggered. Flushing and closing the stream on both sides should ensure that we don't run into this problem and both parties gracefully exit the protocol.	3 years ago
Daniel Karzel	c0070f8fa7	Move files from `protocol` to appropriate module ... Some network and application specific code does not belong in the protocol module and was moved. Eventloop, recovery and the outside behaviour were moved to the respective application module because they are application specific. The `swap_setup` was moved into the network module because upon change both sides will have to be changed and should thus stay close together.	3 years ago