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

Support using the negotiated WebSocket sub-protocol [SPR-10786] #15412

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

Comments

@spring-projects-issues
Copy link
Collaborator

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

Rossen Stoyanchev opened SPR-10786 and commented

Although STOMP is a supported WebSocket sub-protocol, currently it is used irrespective of the sub-protocol that may have been negotiated during the WebSocket handshake.

This is of course convenient if STOMP is the only sub-protocol that an application plans to support. However it should also be possible to have the negotiated sub-protocol determine what is used. That way more than one sub-protocol can be supported and negotiated at runtime.


Affects: 4.0 M2

This issue is a sub-task of #13994

@spring-projects-issues
Copy link
Collaborator Author

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

Rossen Stoyanchev commented

WebSocketSession now provides access to the accepted sub-protocol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web type: task
Projects
None yet
Development

No branches or pull requests

2 participants