pub struct Ready {
pub session_id: String,
pub epoch: u32,
pub ping_interval_ms: u32,
pub pong_timeout_ms: u32,
pub max_missed_pongs: u32,
pub idle_timeout_ms: u32,
pub jitter_ms: u32,
pub max_payload_bytes: u32,
pub max_topics_per_connection: u32,
pub max_send_queue_bytes: u32,
pub server_time: i64,
}Expand description
Server Ready frame – spec §5.5.
The Ready frame is the final handshake frame. It is sent by the
server after the session is fully established (and any resume
exchange is complete). It carries the runtime parameters the client
needs to operate correctly on this connection.
After receiving Ready the client may begin publishing and subscribing to topics.
Fields§
§session_id: StringUnique session identifier assigned by the server.
epoch: u32Monotonically increasing epoch counter for this session.
ping_interval_ms: u32Minimum interval in milliseconds between consecutive Ping frames the client must send.
pong_timeout_ms: u32Maximum time in milliseconds the client should wait for a Pong reply before considering the Ping missed.
max_missed_pongs: u32Number of consecutive missed Pongs that triggers connection teardown on the client side.
idle_timeout_ms: u32Idle timeout in milliseconds; the connection will be closed if no frames are received within this window.
jitter_ms: u32Maximum random jitter in milliseconds to add to the effective ping interval, used to prevent heartbeat synchronization across many clients.
max_payload_bytes: u32Maximum payload size in bytes for a single frame on this connection.
max_topics_per_connection: u32Maximum number of topics this connection may subscribe to simultaneously.
max_send_queue_bytes: u32Maximum size in bytes of the client’s outbound send queue before the server will apply back-pressure or close the connection.
server_time: i64Server wall-clock time in milliseconds since the Unix epoch at the moment the Ready frame was generated.