Oct 14, 2021

The message queues are thus buried in the socket (as with ZeroMQ), maintaining the simplicity of protocol implementation. Ideally we would want to suspend performing work that could not be sent to a peer, but this at least puts an upper bound on the resources that a peer can consume. It will also be possible to provide a cost metric per incoming message type, to limit peer requests by actual resource consumption, suspending the reader until queued work drops below the configured limit.