You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Close connection when keep-alive timeout is reached in graphql-transport-ws protocol of juniper_graphql_ws crate (#1367)
- remake `ConnectionConfig::keep_alive_interval` option as `ConnectionConfig::keep_alive` represented by `KeepAliveConfig`
- consider `ConnectionConfig::keep_alive::timeout` in `graphql-transport-ws` protocol
Co-authored-by: Kai Ren <tyranron@gmail.com>
Copy file name to clipboardExpand all lines: juniper_graphql_ws/CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,13 +12,18 @@ All user visible changes to `juniper_graphql_ws` crate will be documented in thi
12
12
13
13
-`Schema::Context` now requires `Clone` bound for ability to have a "fresh" context value each time a new [GraphQL] operation is started in a [WebSocket] connection. ([#1369])
14
14
> **COMPATIBILITY**: Previously, it was `Arc`ed inside, sharing the same context value across all [GraphQL] operations of a [WebSocket] connection. To preserve the previous behavior, the `Schema::Context` type should be either wrapped into `Arc` or made `Arc`-based internally.
15
+
- Replaced `ConnectionConfig::keep_alive_interval` option with `ConnectionConfig::keep_alive` one as `KeepAliveConfig`. ([#1367])
16
+
- Made [WebSocket] connection closed once `ConnectionConfig::keep_alive::timeout` is reached in [`graphql-transport-ws` GraphQL over WebSocket Protocol][proto-6.0.7]. ([#1367])
17
+
> **COMPATIBILITY**: Previously, a [WebSocket] connection was kept alive, even when clients do not respond to server's `Pong` messages at all. To preserve the previous behavior, the `ConnectionConfig::keep_alive::timeout` should be set to `Duration:::ZERO`.
15
18
16
19
### Fixed
17
20
18
21
- Inability to re-subscribe with the same operation `id` after subscription was completed by server. ([#1368])
0 commit comments