You can choose not to recompile your client applications and continue
to use client libraries from a previous release. If you choose to
use client libraries from a previous release, ensure that the
libraries are compatible with the new server. For more information,
You can choose to upgrade your client applications to use the new client libraries. To do
this, recompile the client applications against the client libraries
located in the clients directory of your new
Diffusion server installation and
repackage your client application with the new library.
The .NET client library is now fully compatible with the .NET Standard 2.0.
Officially supported platforms are Windows (via .NET Framework, .NET Core), MacOS (.NET Core),
and various Linux distributions (via .NET Core). In order to make this change clear we removed the old
PushTechnology.ClientInterface library and NuGet package and replaced it with
This requires re-compilation of your project.
Include browserify-zlib-0.2.0.js for clients that want to make use of the client compression capability.
This can be achieved at build time by using browserify to package the browserify-zlib npm module into the application library.
browserify-zlib-0.2.0.js is included in the clients/js directory
of your Diffusion installation, and can be downloaded from
Clients will log out a warning at startup if browserify-zlib-0.2.0.js is not included.
The client's initial connection request will set the per-message compression capability depending on
whether browserify-zlib-0.2.0.js is included. This will indicate to the server whether messages should be compressed
before they are sent to the client.
The Java client now supports Java 9, 10 and 11. Java 8 is still required for the server.
Some features that your client applications might use have been removed or deprecated.
Review the API changes information
in the following section to see if these changes affect your