Releases · centrifugal/centrifuge-java

04 Aug 04:54

FZambia

0.2.3

b18dacd

0.2.3

Fix reconnect after onFailure #39
Avoid duplicate connecting event, better Exception msg if tokenGetter not set. Commit.
Fixes in example

Assets 2

25 Jul 15:34

FZambia

0.2.2

27374a9

0.2.2 - new SDK API

Breaking changes

Releases 0.2.0 and 0.2.1 were broken - see #36

This release adopts a new iteration of Centrifugal protocol and a new iteration of API. Client now behaves according to the client SDK API specification. The work has been done according to Centrifugo v4 roadmap.

Check out Centrifugo v4 release post that covers the reasoning behind changes.

All the current core features of Centrifugal client protocol are now supported here.

New release only works with Centrifugo >= v4.0.0 and Centrifuge >= 0.25.0. See Centrifugo v4 migration guide for details about the changes in the ecosystem.

Note, that Centrifugo v4 supports clients working over the previous protocol iteration, so you can update Centrifugo to v4 without any changes on the client side (but you need to turn on use_client_protocol_v1_by_default option in the configuration of Centrifugo, see Centrifugo v4 migration guide for details).

Assets 2

21 Jul 06:05

FZambia

0.2.0

dd63003

0.2.0 - new SDK API

This release was broken - see #36. Go to 0.2.2 which fixed the problem.

Assets 2

30 Aug 19:30

FZambia

0.1.0

2b3c332

0.1.0

Update to work with Centrifuge >= v0.18.0 and Centrifugo v3.

Breaking change: client History API behavior changed – Centrifuge >= v0.18.0 and Centrifugo >= v3.0.0 won't return all publications in a stream by default, see Centrifuge v0.18.0 release notes or Centrifugo v3 migration guide for more information and workaround on server-side. History call now accepts options. Example on how to mimic previous behavior:

HistoryOptions opts = new HistoryOptions.Builder().withLimit(-1).build();
subscription.history(opts, ...)

If you are using Centrifuge < v0.18.0 or Centrifugo v2 then default options will work the same way as before - i.e. return all publications in a history stream.

Protocol definitions updated to the latest version
Support for top-level presence, presenceStats and history methods
When working with Centrifugo v3 or Centrifuge >= v0.18.0 it's now possible to avoid using ?format=protobuf in connection URL. Client will negotiate Protobuf protocol with a server using WebSocket subprotocol mechanism (in request headers).
Add ClientInfo to PublishEvent and ServerPublishEvent #29