Client Protocols
Reference the current Gateway lifecycle and WKProto packet boundary.
Clients establish long-lived connections through Gateway TCP or WebSocket listeners. The current public baseline uses the same WKProto semantics for negotiation, send, receive acknowledgement, and heartbeat.
A protocol is not an HTTP API
TCP binary frames and WebSocket messages do not belong in OpenAPI. This section records wire and Gateway behavior without inventing HTTP paths.
Connection Lifecycle
CONNECT-first behavior, CONNACK, active sessions, idle close, and recovery.
Packet Types
FrameType values 0–12, directions, and current publication scope.
TCP Binary Protocol
Fixed header, Remaining Length, field order, and version boundaries.
Encryption & Security
X25519, AES-CBC, msg_key, and security limits.
EasySDK JSON-RPC
Core online path, four-client wire compatibility, and experimental boundaries.
Current boundary
- The public core contains only CONNECT/CONNACK, SEND/SENDACK, RECV/RECVACK, and PING/PONG.
DISCONNECT,SUB, andSUBACKare currently codec contracts, not published product Gateway entry points.- The current product Gateway reserves
EVENTonly for benchmark terminal-fence request and acknowledgement; it is not an application event API. - WebSocket can carry WKProto bytes. The JSON-RPC bridge supports the pinned EasySDK core online path; the matrix marks every other method experimental or missing.
See Shared Dictionaries for numeric meanings and Authentication & Security for the production trust boundary.