Transport Layer

WuKongIM has two easily confused network boundaries. Clients enter through Gateway TCP/WebSocket, while cluster nodes use a separate node Transport for Controller, Slot, Channel, and internal RPC traffic. They have different ports, protocols, identities, and capacity limits.

HTTP API and Manager are separate service entries again. Do not treat client tokens, Manager JWTs, Join Tokens, and node discovery addresses as one authentication mechanism.

Each frame carries kind, priority, service ID, request ID, and body length. Cluster adapters assign fixed service IDs to Controller Raft, Slot Raft, state sync, Channel replication, foreground append, online owner push, and other bounded capabilities. Generic Transport does not interpret business payloads.

• listen_addr controls the local bind and can use 0.0.0.0 or [::] to accept connections.
• advertise_addr, or an address in the static node table, must be a stable endpoint reachable by every peer.
• Discovery resolves node IDs to remote addresses and opens a limited connection pool per peer.
• Controller mirrors, dynamic join, and early startup can use seed or static addresses, while Controller snapshots provide the continuing membership view.

Publishing a bind address produces a node that can listen locally but cannot be reached by peers. See Networking & Client Access for configuration details.

Transport limits frame body size, queued items and bytes per connection, batch frames and bytes, service queues, handler concurrency, and write timeouts. Saturation returns backpressure or closes a failed connection so waiting RPCs wake explicitly.

• Raft and control messages keep low wait and do not join the short coalescing window used by ordinary RPC traffic.
• Foreground Channel append services can use higher bounded concurrency while retaining payload and queue limits.
• Raft protocol services use an ordered handler lane so concurrent handlers cannot reorder peer messages.
• Channel Pull and PullHint can form small same-target batches while preserving item-aligned results and channel fences.

Priority affects scheduling only. It does not bypass authority checks or turn a timed-out request into a known non-execution.

Slot and Channel layers re-resolve Leader or epoch before deciding whether to retry. Transport does not guess a new authority node.

• peer connection count, reconnects, and dial failures;
• scheduler queued items and bytes, batch size, and wait;
• typed RPC latency, timeout, and result;
• service queue, running/capacity, and handler duration;
• layered Channel replication and Raft errors instead of aggregate network throughput alone.

During diagnosis, distinguish "Transport delivered to the remote service" from "the remote state machine committed." The former does not prove the latter.