Skip to content

Commit 3a068b8

Browse files
committed
Update link to stompjs library
Closes gh-28409
1 parent f54b19f commit 3a068b8

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -103,9 +103,9 @@ You can also use the WebSocket transport configuration shown earlier to configur
103103
maximum allowed size for incoming STOMP messages. In theory, a WebSocket
104104
message can be almost unlimited in size. In practice, WebSocket servers impose
105105
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.
109109

110110
Spring's STOMP-over-WebSocket support does this ,so applications can configure the
111111
maximum size for STOMP messages irrespective of WebSocket server-specific message

0 commit comments

Comments
 (0)