0.6.1

0.6.0

Breaking change! This release changes the semantics of working with connection tokens described in Centrifugo v5 release post.

Previously, returning an empty token string from CentrifugeConnectionTokenGetter callback resulted in client disconnection with unauthorized reason.

Now returning an empty string from CentrifugeConnectionTokenGetter is a valid scenario which won't result into disconnect on the client side. It's still possible to disconnect client by returning a special CentrifugeError.unauthorized from CentrifugeConnectionTokenGetter.

And we are putting back SetToken method to the SDK – so it's now possible to reset the token to be empty upon user logout.

0.5.5

0.5.4

0.5.3

0.5.2

0.5.1

0.5.0

Breaking changes

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 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).

Several important changes:

0.4.5

0.4.4

0.4.3

0.4.2

0.4.1

0.4.0

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

Breaking change in server behavior. Client History API behavior changed in Centrifuge >= v0.18.0 and Centrifugo >= v3.0.0. When using history call it 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.

0.3.1

0.3.0

0.2.2

0.2.1

0.2.0

A couple of new methods added to Client.

See more details in pull request #36. In short, subscription removing can be helpful if you work with lots of short-living subscriptions to different channels to prevent unlimited internal Subscription registry growth.

0.1.0

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

0.0.1

Initial library release.