xmr-btc-swap

Commit Graph

Author	SHA1	Message	Date
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
Thomas Eizinger	b417950f99	Improve error reporting of failed protocols Instead of forwarding every error, we deliberately ignore certain variants that are not worth being printed to the log. In particular, this concerns "UnsupportedProtocols" and "ResponseOmission". To make this less verbose we introduce a macro for mapping a `RequestResponseEvent` to `{alice,bob}::OutEvent`. We use a macro because those `OutEvent`s are different types and the only other way of abstracting over them would be to introduce traits that we implement on both of them. To make the macro easier to use, we move all the `From` implementations that convert between the protocol and the more high-level behaviour into the actual protocol module.	3 years ago
Thomas Eizinger	f0f7288bb6	Introduce a `redial::Behaviour` This behaviour makes Bob re-dial Alice with an exponential backoff as soon as the connection is lost.	3 years ago

Author

SHA1

Message

Date

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.

Thomas Eizinger

b417950f99

Improve error reporting of failed protocols

Instead of forwarding every error, we deliberately ignore certain
variants that are not worth being printed to the log. In particular,
this concerns "UnsupportedProtocols" and "ResponseOmission".

To make this less verbose we introduce a macro for mapping a
`RequestResponseEvent` to `{alice,bob}::OutEvent`. We use a macro
because those `OutEvent`s are different types and the only other
way of abstracting over them would be to introduce traits that we
implement on both of them.

To make the macro easier to use, we move all the `From` implementations
that convert between the protocol and the more high-level behaviour
into the actual protocol module.

Thomas Eizinger

f0f7288bb6

Introduce a `redial::Behaviour`

This behaviour makes Bob re-dial Alice with an exponential backoff as
soon as the connection is lost.

3 Commits (620ac569f7db4b19c3dc761619e7a4d0ab0841dd)