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.

Sign up for GitHub

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

Jump to bottom

Issue #2690 - clarify websocket message ordering in documentation #7097

Merged
merged 2 commits into from
Nov 16, 2021
Merged

Issue #2690 - clarify websocket message ordering in documentation #7097

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5bfe2f4
Issue #2690 - clarify websocket message ordering in documentation
lachlan-roberts Nov 11, 2021
c7f09e5
Issue #2690 - changes to documentation from review
lachlan-roberts Nov 12, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions ...entation/jetty-documentation/src/main/asciidoc/programming-guide/websocket.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,8 @@ This event is emitted when the WebSocket communication encounters a fatal error,
Applications interested in the error event receive a `Throwable` that represent the error.
* The _message_ event.
The message event is emitted when a WebSocket message is received.
Only one thread at a time will be delivering a message event to the `onMessage` method; the next message event will not be delivered until the previous call to the `onMessage` method has exited.
Endpoints will always be notified of message events in the same order they were received over the network.
The message event can be of two types:
** Textual message event.
Applications interested in this type of messages receive a `String` representing the UTF-8 bytes received.
Expand Down