AMQP Specification Transport

AMQP Specification.
Session
4 Session
An AMQP Session is a named dialog between two AMQP peers. Each participant maintains a Session
Endpoint that stores the conversational state for that session. Session Endpoints are "attached" when they are
associated with an open Connection. Session Endpoints may become detached deliberately, when a failure
occurs in the network, or when a failure occurs at one of the endpoints. Session Endpoints may be
configured to retain their state either temporarily or permanently when they become detached.
4.1 Naming a Session
Session names are supplied by the initiating peer, and MUST be globally unique among all open sessions.
Once a session is cleanly closed, its may be reused. Session names are represented by opaque binary strings
up to 65535 characters long. Example naming schemes include mechanically generated UUID-based names
as well as stable, manually chosen URI based names. Session names are only exchanged during the attach
and detach procedures, so there is no significant overhead to choosing large names.
4.1.1 session-name: vbin16 (opaque session name)
The session name uniquely identifies an interaction between two peers. It is globally unique among all open
sessions. Once a session is cleanly closed, its name may be reused.
4.2 Establishing a Session
Sessions are established by creating a Session Endpoint, assigning it to an unused channel number, and
sending an ATTACH carrying the state of the newly created Endpoint. The partner responds with an
ATTACH carrying the state of the corresponding Endpoint, creating and/or mapping the Endpoint to an
unused channel number if necessary. To avoid accidentally resuming an existing session, the initiating peer
may optionally wish to verify that the corresponding Endpoint is newly created.
Endpoint
Endpoint
=============================================================
ATTACH(name=..., [CH3]--------->
opening=1, ...) +--[CH7] ATTACH(name=...,
/ opening=1, ...)
/
(1)