Using PubSub+ Messaging APIs with PubSub+ Cache
If you have PubSub+ Cache, you can use the PubSub+ Messaging APIs to make cache requests for topics. The cache requests must include the name of the Distributed Cache, Cache Cluster, or PubSub+ Cache Instance to issue the request to and the topics requested.
Client applications can use the PubSub+ Messaging APIs for JCSMP, Java RTO, C, .NET, or JavaScript to make cache requests for topics. The cache requests must include the name of the Distributed Cache, Cache Cluster, or PubSub+ Cache Instance to issue the request to and the topics requested.
Cache requests made using the JCSMP, Java RTO, C, and .NET APIs can either be synchronous or asynchronous. If the request is synchronous, then the API call blocks until the response is received (or a time-out occurs).
Cache requests made using JavaScript only allows asynchronous cache requests.
If a cache request is made to a Distributed Cache or a Cache Cluster, the request is delivered to one of the PubSub+ Cache Instances in a Cache Cluster that are configured to listen for the same topics, and that single PubSub+ Cache Instance responds to the cache request.
Cache responses are addressed back to the originating client on an automatically generated peer-to-peer topic contained within the request.
The result of a cache request is indicated by return codes or events provided by the Cache Instance. Any messages that are returned for the request are handled through message receive callback or delegate associated with the session that the cache session is created in. For more information about configuring and details about PubSub+ Cache, see PubSub+ Cache.
For information about using PubSub+ Messaging APIs with PubSub+ Cache, see:
For Messaging API versions that are compatible with PubSub+, see PubSub+ Cache Client Support in Feature Support in PubSub+ Messaging APIs.