Vsevolod Brekelov 4e6ed9021c network: add ping pong processing ... add pingInterval same as used in ref C# implementation with the same logic add pingTimeout which is used to check whether pong received. If not -- drop the peer. add pingLimit which is hardcoded to 4 in TCPPeer. It's limit for unsuccessful ping/pong calls (where pong wasn't received in pingTimeout interval)		2020-01-17 13:24:14 +03:00
..
metrics	cli,pkg: use zap.Logger	2020-01-10 11:14:27 +03:00
payload	network: add ping pong processing	2020-01-17 13:24:14 +03:00
blockqueue.go	cli,pkg: use zap.Logger	2020-01-10 11:14:27 +03:00
blockqueue_test.go	cli,pkg: use zap.Logger	2020-01-10 11:14:27 +03:00
discovery.go	monitoring: add prometheus monitoring	2019-10-29 20:51:17 +03:00
discovery_test.go	network: rework discovery with rwmutex, add test	2019-10-28 13:37:27 +03:00
helper_test.go	network: add ping pong processing	2020-01-17 13:24:14 +03:00
message.go	network: add ping pong processing	2020-01-17 13:24:14 +03:00
message_test.go	Node improvements (#47)	2018-03-14 10:36:59 +01:00
peer.go	network: add ping pong processing	2020-01-17 13:24:14 +03:00
prometheus.go	monitoring: add prometheus monitoring	2019-10-29 20:51:17 +03:00
relay_reason.go	fix spelling and godoc comments	2019-10-22 17:56:03 +03:00
server.go	network: add ping pong processing	2020-01-17 13:24:14 +03:00
server_config.go	network: add ping pong processing	2020-01-17 13:24:14 +03:00
server_test.go	cli,pkg: use zap.Logger	2020-01-10 11:14:27 +03:00
tcp_peer.go	network: add ping pong processing	2020-01-17 13:24:14 +03:00
tcp_peer_test.go	network: wait for both Version messages before ACKing	2019-11-06 18:05:50 +03:00
tcp_transport.go	network: fix logic and logging for sendVersion() errors	2020-01-13 17:33:29 +03:00
transport.go	Fixed some networking issues (#68)	2018-04-13 12:14:08 +02:00