-
Notifications
You must be signed in to change notification settings - Fork 594
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
=doc #1818 formatting issue in websocket docs #1820
Conversation
Resolves #1818 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's another one a bit further down: "@scala[`Flow[Message, Message, Any]]]". Should be good after that!
Test PASSed. |
Second, the application can optionally choose one of the proposed application-level sub-protocols by inspecting the | ||
values of @scala[`UpgradeToWebSocket.requestedProtocols`]@java[`UpgradeToWebSocket.getRequestedProtocols`] and pass the chosen protocol value to @scala[`handleMessages`]@java[`handleMessagesWith`]. | ||
|
||
### Handling Messages | ||
|
||
A message handler is expected to be implemented as a @scala[`Flow[Message, Message, Any]]]@java[@unidoc[Flow[Message, Message, ?]]]. For typical request-response | ||
A message handler is expected to be implemented as a @scala[@unidoc[Flow[Message, Message, Any]]]@java[@unidoc[Flow[Message, Message, ?]]]. For typical request-response |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the additional catch @raboof
Test PASSed. |
No description provided.