channels

Connections are bidirectional. Receiving is handled by the incoming handler of the latent connection.

Contains all the information required to try and establish a bidirectional connection. Only misses specification on how to handle messages, the abstract handler is acquired from incoming Note, may produce multiple connections (e.g., if this produces a server connection) thus triggering the async multiple times.

Implementations should make it safe to establish multiple times, though the semantics of that is unclear.

loopSelection and runSelection should not be called from multiple threads at the same time. Only one thread should send on a single connection at the same time.

Provides a specification how to handle messages, given a connection context. Failure calls on the callback generally indicate connection errors on the receiver side.

Allows establishing direct synchronous connections between a single “server” and multiple “clients”.

Synchronous here means that any send calls immediately execute the handler code no the receiving side (after a couple of callback indirections). There is no runtime and no threads and the send call will only return after the handling code has completed.

It does not matter if the server or client is started first, connection is established immediately when the second one joins the connection.