summaryrefslogtreecommitdiff
path: root/qpid/cpp/AMQP_1.0
diff options
context:
space:
mode:
Diffstat (limited to 'qpid/cpp/AMQP_1.0')
-rw-r--r--qpid/cpp/AMQP_1.017
1 files changed, 17 insertions, 0 deletions
diff --git a/qpid/cpp/AMQP_1.0 b/qpid/cpp/AMQP_1.0
index 95f02b8e53..0e811a68f5 100644
--- a/qpid/cpp/AMQP_1.0
+++ b/qpid/cpp/AMQP_1.0
@@ -51,6 +51,9 @@ The name specified in the address supplied when creating a sender or
receiver is used to set the 'address' field of the target or source
respectively.
+The special address name '<null>' can be used to indicate that the
+address hould be left null.
+
If the subject is specified for a sender it is used the default
subject for messages sent without an explicit subject set.
@@ -177,6 +180,20 @@ be created on the broker and bound to the exchange. [See section on
'Topics' below]. The name of the queue will be of the form
<container-id>_<link-name>.
+If the target address of an attaching sender link is null, and the
+dynamic flag is not set, then the broker will route all messages
+received over this sender link using the 'to' field from the
+properties. If that matches the name of a queue, the message will be
+enqueued to that queue. If it doesn't match a queue but matches an
+exchange the message will be routed through that exchange. If it
+doesn't match either a queue or an exchange then it will be
+dropped. This behaviour is known as 'ANONYMOUS-RELAY', a capability
+which the broker advertises in the open frames it sends over every
+connection. To use it the sending process needs to have permission to
+access the ANONYMOUS-RELAY 'pseudo-exchange' (note: there isn't
+actually an exchange of that name, but this is how the capability is
+represented in the ACL permissions model).
+
Outgoing links may have a filter set on their source. The filters
currently supported by the broker are 'legacy-amqp-direct-binding',
'legacy-amqp-topic-binding', 'legacy-amqp-headers-binding',