- All Superinterfaces:
public interface CompatibilityPublisher extends Publisher
This implementation of
Publisheris similar to
ActivePublisher, but because it does not maintain a cache, it passes all requests and discards for subjects on to the
DataProvider. This it calls
DataProviderevery time a peer discards a subject, rather than just once when the final peer discards the subject. This requires your
DataProviderto keep count of the number of peers that are subscribed to a subject and only unsubscribe from the back end system when the subscription count goes to zero.
Note: The use of
CompatibilityPublisheris not recommended; use
CompatibilityPublisheris provided for backwards compatibility with versions of DataSource for Java prior to 5.0, which require you to manage peers yourself. You may want to use this publisher if you are upgrading an existing DataSource application that contains such peer management logic.
Instantiate this interface using the appropriate Caplin API method.