← Back to the chapter · Previous detail · Next detail →
Technical detail · AMQP Frames: Routing and Reliability
AMQP 1.0 connection, session and link fields
These field sketches omit other required fields and are not complete wire encodings. OPEN identifies container client-app-001, supplies the peer hostname and exchanges capabilities and connection limits. Hostname-to-virtual-host interpretation is broker-specific. The example advertises a 65,536-byte maximum frame, channel maximum 32,767 and idle timeout 120,000 ms. Empty frames can keep the connection active. BEGIN multiplexes transfer streams with session ordering and windows. ATTACH creates a named endpoint with source, target and settlement mode; here the sender targets sensor_queue and waits for receiver disposition.
OPEN {
container_id: "client-app-001" # Unique identifier
hostname: "broker.example.com" # Peer hostname; vhost interpretation is broker-specific
max_frame_size: 65536 # Max frame size in bytes
channel_max: 32767 # Highest channel number
idle_time_out: 120000 # Requested maximum idle interval (ms)
}
BEGIN {
remote_channel: null # For new session
next_outgoing_id: 0 # Transfer sequence number
incoming_window: 1000 # Flow control window
outgoing_window: 1000 # Flow control window
}
ATTACH {
name: "sensor-producer-link" # Unique link name
role: sender # sender or receiver
source: { address: null } # Null source in this example
target: { address: "sensor_queue" }# Destination queue
snd_settle_mode: unsettled # Wait for receiver disposition in this example
}