ValencyCounter represents how many active connections we have towards a given peer. It starts out with a positive value representing a desired number of connections for a specific subscription worker. It can become negative, for example if a peer opens multiple connections to us. The vcId is unique per ConnectionTable and ensures that we won't count the same connection twice.

Mutable state maintained by the network component.

Wrapper for OuroborosResponderApplication and OuroborosInitiatorAndResponderApplication.

Clean PeerStates within NetworkMutableState every 200s

Policy which governs how to limit the number of accepted connections.

Connection is identified by local and remote address.

TODO: the type variable which this data type fills in is called peerid. We should renamed to connectionId.

Run a server application. It will listen on the given address for incoming connection, otherwise like withServerNode'.

Run a server application on the provided socket. The socket must be ready to accept connections. The server thread runs using withAsync function, which means that it will terminate when the callback terminates or throws an exception.

TODO: we should track connections in the state and refuse connections from peers we are already connected to. This is also the right place to ban connection from peers which misbehaved.

The server will run handshake protocol on each incoming connection. We assume that each version negotiation message should fit into maxTransmissionUnit (~5k bytes).

Note: it will open a socket in the current thread and pass it to the spawned thread which runs the server. This makes it useful for testing, where we need to guarantee that a socket is open before we try to connect to it.

Common arguments of various variants of connectToNode.

Connect to a remote node. It is using bracket to enclose the underlying socket acquisition. This implies that when the continuation exits the underlying bearer will get closed.

The connection will start with handshake protocol sending Versions to the remote peer. It must fit into maxTransmissionUnit (~5k bytes).

Exceptions thrown by MuxApplication are rethrown by connectToNode.

A version connectToNode which allows one to control which mini-protocols to execute on a given connection.

Connect to a remote node using an existing socket. It is up to to caller to ensure that the socket is closed in case of an exception.

The connection will start with handshake protocol sending Versions to the remote peer. It must fit into maxTransmissionUnit (~5k bytes).

Exceptions thrown by MuxApplication are rethrown by connectTo.

Configure a socket. Either AF_INET or AF_INET6 socket is expected.

Configure sockets passed through systemd socket activation. Currently ReuseAddr and Linger options are not configurable with 'systemd.socket', these options are set by this function. For other socket options we only trace if they are not set.

Tracer used by connectToNode (and derivatives, like connectTo or 'Ouroboros.Network.NodeToClient.connectTo).

Tracers required by a server which handles inbound connections.

Trace for the AcceptConnectionsLimit policy.

Make a server-compatible socket from a network socket.

Accept or reject incoming connection based on the current state and address of the incoming connection.

A record that holds handshake callbacks.

Map from addresses to PeerStates; it will be be shared in a StrictTVar.

Abstracting t is useful for tests, the IO version will use Time IO.

Insert a new connection into the ConnectionTable.

Create a new ValencyCounter

Add a connection.

Remove a connection.

Wait until ValencyCounter becomes positive, used for detecting when we can create new connections.

Returns current ValencyCounter value, represent the number of additional connections that can be created. May be negative.