Pierre-Marie Padiou f3b746643d Use TCP pull mode (#422) ... We now use [akka tcp pull mode](https://doc.akka.io/docs/akka/2.5.3/scala/io-tcp.html#read-back-pressure-with-pull-mode) for both incoming and outgoing connections. In combination with setting a relatively low value for `akka.io.tcp.max-received-message-size`, this results in less RAM consumption, in particular when validating a whole routing table. Also improved the router: - Removed the grouping of `channel_announcement` because batching is done lower in the stack, in the bitcoin json-rpc client. Channels are now validated as they arrive. - Keep track of all origin peers for every announcement (instead of the first one), in order not to send back the same announcements to peers. - Better choice of data structures, which increases constant time operation (but don't completely eliminate less efficient access) - Reworked management of private/not-yet-announced channels		2018-02-16 15:49:34 +01:00
..
src/main	Use TCP pull mode (#422)	2018-02-16 15:49:34 +01:00
pom.xml	back to SNAPSHOT	2018-01-23 19:11:06 +01:00