Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for sending direct messages to connected STOMP clients [SPR-10750] #15376

Closed
spring-projects-issues opened this issue Jul 16, 2013 · 1 comment
Assignees
Labels
in: messaging in: web type: task
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

@spring-projects-issues spring-projects-issues commented Jul 16, 2013

Rossen Stoyanchev opened SPR-10750 and commented

When application code needs to send a message to a STOMP client connected over WebSocket, it has no access to information such as the WebSocket session (and sessionId) or even which server the client is connected to. This may be needed in an exception handling method, or in an asynchronously executing method that needs to target the user (e.g. with a trade confirmation).

This ticket should make it easy to send messages to a specific user from anywhere within the application.


Affects: 4.0 M1

This issue is a sub-task of #13994

@spring-projects-issues
Copy link
Collaborator Author

@spring-projects-issues spring-projects-issues commented Jul 18, 2013

Rossen Stoyanchev commented

The support in M2 is enabled through a messaging template that accepts a user name and target destination. There is also an @ReplyToUser annotation that sends the return value as a message to the specified destination based on the currently logged in user.

@spring-projects-issues spring-projects-issues added in: messaging in: web type: task labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 4.0 M2 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: messaging in: web type: task
Projects
None yet
Development

No branches or pull requests

2 participants