Package-level declarations
Types
The ClusterChannel over HTTP: a forward is a POST of its JSON to InternalHttp.FORWARD_PATH on the peer's internal port, through the JDK client (HTTP/2 over h2c).
Sends wait signals to the internal signal entry (InternalHttp.SIGNALS_PATH) of the node a wait started on, at its Origin.address: the remote of a me.ahoo.wow.runtime.wait.LocalSignalSender. A signal is written by ClusterCodec, as every message between the nodes of a service.
The internal port: the cluster channel and the wait signal entry of a node, served apart from its public port, over HTTP/1.1 and h2c. A node names its service on each request (Wow-Service); the port is reachable by the platform's own pods alone, a NetworkPolicy's boundary, not a token's.
The internal port of the node: a Reactor Netty server of its own, apart from the public WebFlux server, serving its routes (the cluster channel, the wait signals, the services' calls and peer reads) over HTTP/1.1 and h2c. Its codecs take messages of up to InternalPortSettings.maxMessageSize bytes, which a host derives from the public port's codec limit (InternalHttp.messageLimit), and the server takes an upgrade request of up to that size too, as the JDK client reaches HTTP/2 by upgrading the first request of a connection. It takes InternalHttp.MAX_CONCURRENT_STREAMS streams on a connection at a time, the limit the node's senders keep within. It keeps Netty's guard against rapid resets: a connection on which it reads more than 200 RST_STREAM frames in 30 seconds is closed.
What an InternalPort is built of: the port it binds (0 for one the system chooses) on bindHost, and the maxMessageSize of its codecs.
A node's standby, as its operator routes see it.
Functions
The routes of the internal port:
The routes of the internal port, its signals taken by registry, the waits started on this node.