The 'transport' is somewhat conceptual and handles generating/sending/receiving the AMQP frames/protocol bytes over the TCP transport connection, based on the activity of the related AMQP 'connection' object and its children, with these all relating closely to actual AMQP protocol entities. The connection can have sessions, on which actual senders and receivers are created and send/receive messages. The callbacks relate to each of these entities being opened against the peer (e.g a broker). Some of the APIs simplify this by creating a 'default session' to allow dealing more directly with creating senders and receivers on.
On Thu, 8 Jun 2023 at 11:50, Tiaan Wessels <tiaanwess...@gmail.com> wrote: > > Hi, > What is the differences between > on_transport/connection/session/sender/receiver_open? The docs are scant on > explanations. > Thanks --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
