Data Publishing

Subscription based Publishers

Compatibility Publisher

The ICompatibilityPublisher passes all requests and discards from remote DataSource peers to the IDataProvider. The IDataProvider implementation is responsible for keeping track of the number of requests received; it must only stop supplying data for a subject when there are no peers subcribing to it.

This publisher implementation corresponds to the behaviour of the DataSource 4.4 API.

An ICompatibilityPublisher can be created using the Caplin.DataSource.DataSource.CreateCompatibilityPublisher method.

Active Publisher

The IActivePublisher passes all requests and the discard corresponding to the last DataSource peer to unsubscribe to the IDataProvider. The IDataProvider implementation is responsible for keeping track of the number of requests received; it must only stop supplying data for a subject when there are no peers subcribing to it.

An IActivePublisher can be created using the Caplin.DataSource.DataSource.CreateActivePublisher method.

Broadcast Publisher

The BroadcastPublisher will publish messages to all connected DataSource peers. The use of an IBroadcastPublisher is not recommended due to the detrimental effects that broadcast data has on reliable and predictable failover between DataSource components.

Caching Publisher

The ICachingPublisher passes the initial request and the discard corresponding to the last DataSource peer to unsubscribe to the IDataProvider. The IDataProvider implementation does not neet to keep track of the number of requests received; it must only stop supplying data for a subject when there are no peers subcribing to it. When the ICachingPublisher publishes an initial message it saves the message to cache. Subsequent published updates are applied to the cache. If a request is received from a new peer for in-cache data then the data in the cache is set to that peer

An ICachingPublisher can be created using the Caplin.DataSource.DataSource.CreateCachingPublisher method.