root
/
rabbitmq-server
mirror of https://github.com/rabbitmq/rabbitmq-server.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

cosmetic: avoid long lines

This commit is contained in:
Marek Majkowski 2010-11-04 12:17:40 +00:00
parent b7af8226b8
commit 8ca7b1b5ae
1 changed files with 42 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

58
deps/rabbitmq_stomp/DESIGN.md vendored
View File

@ -1,43 +1,69 @@
# STOMP Adapter Enhancements
This document outlines proposed changes to the way in which the STOMP adapter handles destinations and routing.
This document outlines proposed changes to the way in which the STOMP
adapter handles destinations and routing.
IMPORTANT: Support for all existing custom headers will be removed.
IMPORTANT: Support for all existing custom headers will be removed.
## Destinations
In the current STOMP adapter, much of the destination configuration is handled by custom headers, including `routing_key` and `exchange`.
## Destinations
In the current STOMP adapter, much of the destination configuration is
handled by custom headers, including `routing_key` and `exchange`.
This design proposes to remove the custom headers, and use only the
`destination` header with compound values that define the exchange,
routing key and queue names.
This design proposes to remove the custom headers, and use only the `destination` header with compound values that define the exchange, routing key and queue names.
### Standard AMQP Destinations
Any exchange/queue or exchange/routing key combination can be accessed using destinations prefixed with `/exchange`.
Any exchange/queue or exchange/routing key combination can be accessed
using destinations prefixed with `/exchange`.
For `SUBSCRIBE` frames, a destination of the form `/exchange/<name>[/<pattern>]` can be used. This destination will:
For `SUBSCRIBE` frames, a destination of the form
`/exchange/<name>[/<pattern>]` can be used. This destination will:
1. Create an anonymous, auto-delete queue on `<name>` exchange.
2. If `<pattern>` is supplied, bind the queue to `<name>` exchange using `<pattern>`
2. If `<pattern>` is supplied, bind the queue to `<name>` exchange
using `<pattern>`
3. Register a subscription against the queue, for the current STOMP session
For `SEND` frames, a destination of the form `/exchange/<name>[/<routing-key>]` can be used. This destination will:
For `SEND` frames, a destination of the form
`/exchange/<name>[/<routing-key>]` can be used. This destination will:
1. Send to exchange `<name>`with the routing key `<routing-key>`
### Queue Destinations
For simple queue destinations with round-robin delivery semantics, destinations of the form `/queue/<name>` can be used.
For simple queue destinations with round-robin delivery semantics,
destinations of the form `/queue/<name>` can be used.
For both `SEND` and `SUBSCRIBE` frames, these destinations will create the queue `<name>`.
For both `SEND` and `SUBSCRIBE` frames, these destinations will create
the queue `<name>`.
For `SEND` frames, the message will be sent to the default exchange with the routing key `<name>`. For `SUBSCRIBE` frames, a subscription against the queue `<name>` will be created for the current STOMP session.
For `SEND` frames, the message will be sent to the default exchange
with the routing key `<name>`. For `SUBSCRIBE` frames, a subscription
against the queue `<name>` will be created for the current STOMP
session.
Given that both `SEND` and `SUBSCRIBE` frames cause the queue to be
created, the ordering constraint, client codes doesn't need to worry
about creating a subscription before sending messages. Furthermore,
the created queues are set to `auto-delete=false` so they will last
until they are deleted by the user.
Given that both `SEND` and `SUBSCRIBE` frames cause the queue to be created, the ordering constraint, client codes doesn't need to worry about creating a subscription before sending messages. Furthermore, the created queues are set to `auto-delete=false` so they will last until they are deleted by the user.
### Topic Destinations
For simple topic destinations which deliver a copy of each message to all active subscribers, destinations of the form `/topic/<name>` can be used.
For simple topic destinations which deliver a copy of each message to
all active subscribers, destinations of the form `/topic/<name>` can
be used.
For `SEND` frames, the message will be sent to the `amq.topic` exchange with the routing key `<name>`.
For `SEND` frames, the message will be sent to the `amq.topic`
exchange with the routing key `<name>`.
For `SUBSCRIBE` frames, an exclusive queue will be created and bound to the `amq.topic` exchange with routing key `<name>`. A subscription will be created against the exclusive queue.
For `SUBSCRIBE` frames, an exclusive queue will be created and bound
to the `amq.topic` exchange with routing key `<name>`. A subscription
will be created against the exclusive queue.