File tree Expand file tree Collapse file tree 1 file changed +3
-3
lines changed
framework-docs/modules/ROOT/pages/web/websocket/stomp Expand file tree Collapse file tree 1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -103,9 +103,9 @@ You can also use the WebSocket transport configuration shown earlier to configur
103
103
maximum allowed size for incoming STOMP messages. In theory, a WebSocket
104
104
message can be almost unlimited in size. In practice, WebSocket servers impose
105
105
limits -- for example, 8K on Tomcat and 64K on Jetty. For this reason, STOMP clients
106
- ( such as the JavaScript https://github.com/JSteunou/webstomp-client[webstomp-client]
107
- and others) split larger STOMP messages at 16K boundaries and send them as multiple
108
- WebSocket messages, which requires the server to buffer and re-assemble.
106
+ such as https://github.com/stomp-js/stompjs[`stomp-js/stompjs`] and others split larger
107
+ STOMP messages at 16K boundaries and send them as multiple WebSocket messages,
108
+ which requires the server to buffer and re-assemble.
109
109
110
110
Spring's STOMP-over-WebSocket support does this ,so applications can configure the
111
111
maximum size for STOMP messages irrespective of WebSocket server-specific message
You can’t perform that action at this time.
0 commit comments