Spring/spring-framework
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix documentation issue for user destinations.

Browse Source 
Issue: SPR-11992
This commit is contained in:
Rossen Stoyanchev
2014-07-31 17:15:52 -04:00
parent fbf24a927d
commit 96efafef97
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/asciidoc/index.adoc
View File

@@ -38158,16 +38158,16 @@ so that their session is associated with a concrete user name.
See the previous section on information about authentication.
Spring's STOMP support recognizes destinations prefixed with `/user/`.
For example, a client can subscribe to destination `/user/position-updates`.
For example, a client can subscribe to destination `/user/queue/position-updates`.
This destination will be handled by the `UserDestinationMessageHandler` and
transformed into a destination unique to the user's session,
e.g. `/user/position-updates-123`. This provides the convenience of subscribing
e.g. `/queue/position-updates-123`. This provides the convenience of subscribing
to a generically named destination, while also ensuring that it doesn't "collide"
with any other user that also subscribes to `/user/position-updates`
with any other user that also subscribes to `/user/queue/position-updates`
in order to receive stock position updates unique to them.
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 the same unique destination
belonging to the specified user name.