Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

NO-JIRA fix STOMP doc formatting

This commit is contained in:
Justin Bertram 2024-02-08 11:28:10 -06:00
parent 460faf50fd
commit 311e9382a2
No known key found for this signature in database
GPG Key ID: F41830B875BB8633
1 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/user-manual/stomp.adoc
View File

@ -46,15 +46,13 @@ Follow xref:logging.adoc#configuring-a-specific-level-for-a-logger[these steps]
The STOMP specification is intentionally ambiguous about message routing semantics.
When providing an overview of the protocol the STOMP 1.2 specification https://stomp.github.io/stomp-specification-1.2.html#Protocol_Overview[says]:
----
____
A STOMP server is modelled as a set of destinations to which messages can be sent.
The STOMP protocol treats destinations as opaque string and their syntax is
server implementation specific. Additionally STOMP does not define what the
delivery semantics of destinations should be. The delivery, or
"message exchange", semantics of destinations can vary from server to server and
even from destination to destination. This allows servers to be creative with the
semantics that they can support with STOMP.
----
The STOMP protocol treats destinations as opaque string and their syntax is server implementation specific.
Additionally STOMP does not define what the delivery semantics of destinations should be.
The delivery, or "message exchange", semantics of destinations can vary from server to server and even from destination to destination.
This allows servers to be creative with the semantics that they can support with STOMP.
____
Therefore, there are a handful of different ways to specify which semantics are desired both on the client-side and broker-side.