Skip to content

Commit f4d24f5

Browse files
committed
changelog for v0.25.0
1 parent 62e537c commit f4d24f5

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

changelog.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,29 @@
1+
v0.25.0
2+
=======
3+
4+
**Breaking changes**
5+
6+
This release enables using client protocol v2.
7+
8+
All SDKs in Centrifugal ecosystem now behave according to the client [SDK API specification](https://centrifugal.dev/docs/transports/client_api). The work has been done according to [Centrifugo v4 roadmap](https://github.com/centrifugal/centrifugo/issues/500).
9+
10+
Check out [Centrifugo v4 release post](https://centrifugal.dev/blog/2022/07/19/centrifugo-v4-released) that covers the reasoning behind changes here.
11+
12+
This means:
13+
14+
* WebSocket handler will assume client connects over protocol v2. But we will still support client protocol v1 for some time (I believe half a year at least). Protocol v1 may be forced using `WebsocketConfig.ProtocolVersion` option (set it to `ProtocolVersion1`). Or client can provide `?cf_protocol_version=v1` in connection URL. Applications can smoothly migrate to new protocol, for example, see how [Centrifugo v4 migration guide](https://centrifugal.dev/docs/getting-started/migration_v4) provides steps to migrate apps to new client protocol.
15+
* The same applies to SockJS handler. SockJS is now DEPRECATED in Centrifugal ecosystem (we provide our own WebSocket emulation layer, which is faster, does not require sticky sessions, has less overhead in terms of network traffic and memory usage on server side)
16+
* All examples in this repo were adapted to use the latest client SDK API which works according to new [client SDK spec](https://centrifugal.dev/docs/next/transports/client_api)
17+
* Unidirectional transport examples were also updated and now use client protocol v2
18+
* New SDKs that work with new client protocol will be released in parallel with Centrifuge v0.25.0 and Centrifugo v4
19+
20+
To summarise:
21+
22+
1. Current SDKs will be able to work with Centrifuge v0.25.0 – but you will need to turn on using client protocol v1 on server side. This way you can update server side without changing client side code.
23+
2. New client SDKs which will be released will only work with new iteration of client protocol
24+
25+
Please don't hesitate to join our Telegram and Discord communities in case of questions - we will try to help.
26+
127
v0.24.0
228
=======
329

0 commit comments

Comments
 (0)