A-MQ 6: STOMP destination format
Issue
The STOMP protocol does not mandate any particular interpretation of the destination:
header (e.g., in a SUBSCRIBE
frame). The interpretation of the destination is stated to be vendor-specific. How does A-MQ 6.x interpret this header?
Environment
- Red Hat JBoss A-MQ
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.