[qpid-dispatch] branch master updated: DISPATCH-1792 - Explain undeliverable-here behavior. This closes #867.

[gm...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

gmurthy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/qpid-dispatch.git


The following commit(s) were added to refs/heads/master by this push:
     new 7280cef  DISPATCH-1792 - Explain undeliverable-here behavior. This closes #867.
7280cef is described below

commit 7280cef4c0f60553b7b052adb2bd1d22059ac44c
Author: Paul Wright <pw...@redhat.com>
AuthorDate: Wed Oct 7 10:42:19 2020 +0100

    DISPATCH-1792 - Explain undeliverable-here behavior. This closes #867.
---
 .../modules/user-guide/how-router-enables-brokered-messaging.adoc   | 3 +++
 docs/books/modules/user-guide/how-routers-route-messages.adoc       | 6 ++++++
 2 files changed, 9 insertions(+)

diff --git a/docs/books/modules/user-guide/how-router-enables-brokered-messaging.adoc b/docs/books/modules/user-guide/how-router-enables-brokered-messaging.adoc
index 67caea7..1cde5f6 100644
--- a/docs/books/modules/user-guide/how-router-enables-brokered-messaging.adoc
+++ b/docs/books/modules/user-guide/how-router-enables-brokered-messaging.adoc
@@ -28,6 +28,9 @@ Brokered messaging enables {RouterName} to store messages on a broker queue. Thi
 
 An autolink is a link that is automatically created by the router to attach to a waypoint address. With autolinks, client traffic is handled on the router, not the broker. Clients attach their links to the router, and then the router uses internal autolinks to connect to the queue on the broker. Therefore, the queue will always have a single producer and a single consumer regardless of how many clients are attached to the router.
 
+Using autolinks is a form of _message routing_, as distinct from _link routing_.
+It is recommended to use link routing if you want to use semantics associated with a consumer, for example, the `undeliverable-here=true` modified delivery state.
+
 .Brokered messaging
 image::brokered-messaging.png[Brokered Messaging, align="center"]
 
diff --git a/docs/books/modules/user-guide/how-routers-route-messages.adoc b/docs/books/modules/user-guide/how-routers-route-messages.adoc
index f426ed7..81fa056 100644
--- a/docs/books/modules/user-guide/how-routers-route-messages.adoc
+++ b/docs/books/modules/user-guide/how-routers-route-messages.adoc
@@ -64,6 +64,12 @@ Flow control is "real" in that credits flow across the link route from the recei
 * Server-side selectors
 +
 With a link route, consumers can provide server-side selectors for broker subscriptions.
+
+* Consumer specific acknowledgements
++
+With a link route, modified delivery states can be interpreted by a broker.
+For example, a broker can prevent redelivery of any messsages with the `undeliverable-here=true` modified delivery state.
+
 --
 
 .Additional resources


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org