root
/
spring-framework
mirror of https://github.com/spring-projects/spring-framework.git
1
0
Fork 0
Code Issues Actions 18 Packages Projects Releases Wiki Activity

Update link to stompjs library 

Closes gh-28409
This commit is contained in:
rstoyanchev 2023-11-24 14:44:12 +00:00
parent 9eb2f29d4a
commit 54ecbb2bc8
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
framework-docs/modules/ROOT/pages/web/websocket/stomp/configuration-performance.adoc
View File

@ -103,9 +103,9 @@ You can also use the WebSocket transport configuration shown earlier to configur
maximum allowed size for incoming STOMP messages. In theory, a WebSocket maximum allowed size for incoming STOMP messages. In theory, a WebSocket
message can be almost unlimited in size. In practice, WebSocket servers impose message can be almost unlimited in size. In practice, WebSocket servers impose
limits -- for example, 8K on Tomcat and 64K on Jetty. For this reason, STOMP clients limits -- for example, 8K on Tomcat and 64K on Jetty. For this reason, STOMP clients
(such as the JavaScript https://github.com/JSteunou/webstomp-client[webstomp-client] such as https://github.com/stomp-js/stompjs[`stomp-js/stompjs`] and others split larger
and others) split larger STOMP messages at 16K boundaries and send them as multiple STOMP messages at 16K boundaries and send them as multiple WebSocket messages,
WebSocket messages, which requires the server to buffer and re-assemble. which requires the server to buffer and re-assemble.
Spring's STOMP-over-WebSocket support does this ,so applications can configure the Spring's STOMP-over-WebSocket support does this ,so applications can configure the
maximum size for STOMP messages irrespective of WebSocket server-specific message maximum size for STOMP messages irrespective of WebSocket server-specific message