-
Notifications
You must be signed in to change notification settings - Fork 566
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 for longer WebSocket frames #8025
Conversation
webserver/websocket/src/main/java/io/helidon/webserver/websocket/WsConnection.java
Outdated
Show resolved
Hide resolved
webserver/websocket/src/main/java/io/helidon/webserver/websocket/WsConnection.java
Outdated
Show resolved
Hide resolved
1. Support for writing WS frames of more than 125 bytes, i.e. with lengths that fit in two bytes and eight bytes. 2. Configuration of max-frame-length to limit the size of a frame read by the server. The JDK WS client splits a long payload into 16K frames. 3. Some new tests for (1) and (2).
…classpath. Signed-off-by: Santiago Pericasgeertsen <santiago.pericasgeertsen@oracle.com>
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.
A small possible improvement, fine otherwise
.config() | ||
.protocols() | ||
.stream() | ||
.filter(p -> p instanceof WsConfig) |
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.
You could work around the ugly cast by doing (after filter)
.map(WsConfig.class::cast)
which will change the stream to correctly typed one.
Description
Related to issue #7986.
Documentation
JavaDoc has been updated.