From 70ccbbfab13e4546462fcbfcd7cb83db2fce746b Mon Sep 17 00:00:00 2001 From: Rossen Stoyanchev Date: Thu, 31 Jul 2014 17:12:32 -0400 Subject: [PATCH] Fix documentation issue for user destinations Issue: SPR-11992 --- src/asciidoc/index.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/asciidoc/index.adoc b/src/asciidoc/index.adoc index cc43ef06810..f412e720d18 100644 --- a/src/asciidoc/index.adoc +++ b/src/asciidoc/index.adoc @@ -38534,16 +38534,16 @@ be plugged in (see examples in <>). An application can send messages targeting a specific user. Spring's STOMP support recognizes destinations prefixed with `"/user/"`. -For example, a client might subscribe to the destination `"/user/position-updates"`. +For example, a client might subscribe to the destination `"/user/queue/position-updates"`. This destination will be handled by the `UserDestinationMessageHandler` and transformed into a destination unique to the user session, -e.g. `"/user/position-updates-user123"`. This provides the convenience of subscribing +e.g. `"/queue/position-updates-user123"`. This provides the convenience of subscribing to a generically named destination while at the same time ensuring no collisions with other users subscribing to the same destination so that each user can receive unique stock position updates. On the sending side messages can be sent to a destination such as -`"/user/{username}/position-updates"`, which in turn will be translated +`"/user/{username}/queue/position-updates"`, which in turn will be translated by the `UserDestinationMessageHandler` into one or more destinations, one for each session associated with the user. This allows any component within the application to send messages targeting a specific user without necessarily knowing anything more