Author | SHA1 | Message | Date |
---|---|---|---|
Alexander Simmerl | 9b9022f8df |
privVal: Improve SocketClient network code (#1315)
Follow-up to feedback from #1286, this change simplifies the connection handling in the SocketClient and makes the communication via TCP more robust. It introduces the tcpTimeoutListener to encapsulate accept and i/o timeout handling as well as connection keep-alive, this type could likely be upgraded to handle more fine-grained tuning of the tcp stack (linger, nodelay, etc.) according to the properties we desire. The same methods should be applied to the RemoteSigner which will be overhauled when the priv_val_server is fleshed out. * require private key * simplify connect logic * break out conn upgrades to tcpTimeoutListener * extend test coverage and simplify component setup |
7 years ago |
Alexander Simmerl |
589781721a
|
Invert privVal socket communication
Follow-up to #1255 aligning with the expectation that the external signing process connects to the node. The SocketClient will block on start until one connection has been established, support for multiple signers connected simultaneously is a planned future extension. * SocketClient accepts connection * PrivValSocketServer renamed to RemoteSigner * extend tests |
7 years ago |
Alexander Simmerl | a14aab67de | Integrate PrivValidator socket server | 7 years ago |
Alexander Simmerl | a1020307a0 | Clean up flags | 7 years ago |
Alexander Simmerl | 7d71e702d8 | Integrate privVal client with node secret | 7 years ago |
Alexander Simmerl | fec541373d | Correct server protocol | 7 years ago |
Ethan Buchman | 23eb84db35 | wip: priv val via sockets | 7 years ago |