When you get Diffusion Cloud through AppDirect, you can choose which geographic region your Diffusion Cloud service is hosted in. This enables you to get the best latency for your customers and to ensure that any legal requirements regarding the location of your data and your customers' data are met.

Currently, the available regions are Europe and Australia. If you require a different region, contact [email protected].

For more information, see Getting Diffusion Cloud with AppDirect.

The JavaScript API now includes TypeScript definitions. These definitions enable developers to more efficiently develop JavaScript clients for Diffusion Cloud while minimizing the risk of runtime errors caused by type mismatches.

For more information, see JavaScript.

You can specify that your client attempts connection using more than one transport. If a connection attempt using the first specified transport fails, the client cascades to the next specified transport and uses it to attempt connection.

For more information, see Connecting basics.

You can now create and subscribe to JSON and binary topics using the Apple API.

For more information, see JSON topics and Binary topics.

The relationship between topics and the topic tree has changed significantly in this release.

In previous releases, creating a topic at a topic path – for example, a/b – required that there was a topic at all parent paths – for example, a. If not present, these parent topics were created as stateless topics at the time the child topic was created.

From Diffusion Cloud version 5.9, a topic can be created at any topic path where there is not an existing topic. No additional parent topics are created. Empty intermediate topic paths remain empty and topics can be created at these empty paths at a later point.

Because there is no longer a requirement for every topic to have a parent topic, topics can now be deleted without affecting or deleting any child topics.

For more information, see Connections on IBM Bluemix.

Diffusion Cloud now re-synchronizes the streams of messages from client to Diffusion Cloud and from Diffusion Cloud to client when the client reconnects. When reconnecting, the client notifies Diffusion Cloud of the last message received and the earliest message it can send again. Diffusion Cloud sends any missing messages again and instructs the client to resume from the appropriate message.

The Android and Java API clients also maintain a buffer of messages that can be sent again to Diffusion Cloud.

If any messages have been lost, Diffusion Cloud aborts the reconnection. If reconnection succeeds, no messages have been lost.

For more information, see Reconnect to Diffusion Cloud

JSON and binary topics are now fully supported by the .NET API.

For more information, see JSON topics and Binary topics.

Diffusion Cloud can now be bought through AppDirect on datacenters based in the EU.

For more information, see Getting Diffusion Cloud with AppDirect.

Multi-datacenter support, only available with paid editions of Diffusion Cloud, enables client sessions and the R/ branch of your topic tree to be replicated in a different data center. If the datacenter hosting your Diffusion Cloud service fails, the replicated data is used to recover your service within seconds and clients can reconnect without losing their session.

For more information, see Multi-datacenter replication.

The billing model for data usage has changed to be based only on the bytes that you use instead of on a combination of number of messages and average message size. This simplification of our billing model enables you to more easily estimate the cost of your monthly usage.

For more information, see https://www.pushtechnology.com/pricing/.

A new topic type that enables you to stream your data as JSON or CBOR.

For more information, see JSON topics.

A new topic type that enables you to stream your data as binary.

For more information, see Binary topics.

This topic type enables you to map topic subscriptions to another topic on a client-by-client basis.

For more information, see Routing topics.

This topic type acts as an alias to another topic, the master topic.

For more information, see Slave topics.

A C version of the API is now available for Linux™, Windows™, and OS X^®/macOS^®.

For more information, see .

The Apple API now has the capability to create, update, and delete topics.

For more information, see Apple.

The JavaScript API now supports connecting to Diffusion Cloud using the HTTP polling transport. You can specify that your client attempts connection using more than one transport. If a connection attempt using the first specified transport fails, the client cascades to the next specified transport and uses it to attempt connection.

For more information, see Connecting basics.

The Android client now supports Android 4.1 and later.

Android 4.4 and later are fully supported. Android 4.1, 4.2, and 4.3 are supported on a best-effort basis.

For more information, see Listening for topic events.

For more information, see Example: Make exclusive updates to a topic.

An Apple version of the API is now available for iOS and OS X/macOS.

For more information, see Apple.

The Java version of the API is now available for Android.

For more information, see Android.

For more information, see Real-time metrics.

For more information, see Monitoring your Diffusion Cloud usage from the Diffusion Cloud Dashboard.

For more information, see Viewing the logs from the Diffusion Cloud Dashboard.