TCP server API

[NiteshKant]

This issue is for discussing API for a TCP server.

(This is a dual of #2 which is the client API for TCP and hence shares multiple concepts, which are here for completeness at the cost of repetition)

Intention

To define how TCP must be modeled from a server point of view, using reactive-streams-jvm SPI.

What it is?

An abstraction over:

• How to start a server?
• How to shutdown a server?
• How to process a TCP connection, upon receipt?
• How to write to a TCP connection?
• How to read from a TCP connection?

What it is not?

In general it should not try to arbitrate different standards across different networking libraries. A few examples of that being:

• Define what are the ways to configure a connection, eg: connect timeout, socket backlog, etc. Netty has Channel Options, xnio has Options.
• Define the stages of a connect process i.e how should a physical connection be created.
• Define how does data get read or written over a physical connection.