Skip to content

Commit d67f080

Browse files
sdeleuzerstoyanchev
authored andcommitted
Update WebSocket engines support documentation
1 parent 2c1d5ef commit d67f080

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

src/asciidoc/index.adoc

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -36812,8 +36812,9 @@ WebSocket clients or to a specific user.
3681236812
[[websocket-server]]
3681336813
=== WebSocket Server
3681436814
The Spring Framework provides a WebSocket API designed to adapt to various WebSocket engines.
36815-
For example, it runs on JSR-356 runtimes such as Tomcat (7.0.47+) and GlassFish (4.0+) but
36816-
can also adapt to other WebSocket runtimes such as the Jetty (9.0+) native WebSocket support.
36815+
For example, it runs on JSR-356 runtimes such as Tomcat (7.0.47+), GlassFish (4.0+) and
36816+
WildFly (8.0+) but can also adapt to other WebSocket runtimes such as the Jetty (9.1+)
36817+
native WebSocket support.
3681736818

3681836819
[NOTE]
3681936820
====
@@ -37001,7 +37002,7 @@ requests -- such as Spring MVC's `DispatcherServlet`.
3700137002
This is a significant limitation of JSR-356 that Spring's WebSocket support
3700237003
addresses by providing a server-specific `RequestUpgradeStrategy` even when
3700337004
running in a JSR-356 runtime. At present such support is available on
37004-
Tomcat 7.0.47+, Jetty 9.0+, and GlassFish 4.0+. Additional support will be
37005+
Tomcat 7.0.47+, Jetty 9.1+, GlassFish 4.0+, and WildFly 8.0+. Additional support will be
3700537006
added as more WebSocket runtimes become available.
3700637007

3700737008
[NOTE]

0 commit comments

Comments
 (0)