TCP flow control, supervision and configuration

[everydaysasaturday]

It would be more reliable if the TCP responses would handled by activating the socket.
In high loads and in cases where the response handling takes a bit more time than what it should the tcp stack might overflow. This would then cause the response handler most likely to crash and client would fail to function. So also a supervisor would be needed. And what about configurable connection properties?

[iamaleksey]

@bitchslap It's pretty low-level right now (but without any known unresolved issues). More high-level functionality will be added eventually, once I'm done with my unresolved 2.1 Cassandra issues (in fact, I'm planning to spend several weeks to a month working full time on seestar soon).

Currently, however, nothing's stopping you from wrapping a seestar_connection process into a more high-level module, and/or sticking it into a supervisor. Use seestar_connection as a working building block.