AMQP Term | Universal Messaging Term | Comments |
Container | AMQP Client or UM Realm | UM Realms receive but do not initiate connections over AMQP |
Connection | AMQP Connection | TCP and SSL Web socket, Session Multiplexing and negotiated TLS not supported |
Session | Logical mapping to UM session | An AMQP session is mapped to a native UM session. Currently this is limited to one per connection (no multiplexing) |
Link (inbound) | Publications | Delivery resumption and Message fragmentation not supported |
Link (outbound) | Subscriptions | Link credit values < 100 not reliably supported Delivery resumption and Message fragmentation not currently supported |
Source (on broker) | Queue or Topic on realm | Data groups are not supported |
Target (on broker) | Queue or Topic on realm | Data groups are not supported |
Delivery | The delivery of a message in either direction (pub or sub) | Link recovery is currently unsupported. |
Message | A UM message | Message fragmentation is currently unsupported. |
Not addressed in AMQP specification | Clustering | May require additional client capability Requires specific testing for UM |
Not addressed in AMQP specification | Follow the master Paused publishing | UM specific capability Requires specific support in the client |
Not addressed in AMQP specification | Zones Joins (including filtered) | UM specific capability Requires complete transformation of AMQP messages Requires specific testing for UM |