Caplin.DataSource.Publisher.IBroadcastPublisher Interface Reference

This implementation of IPublisher sends (broadcasts) updates to all connected peers regardless of whether they have requested (subscribed to) the subject. More...

Inheritance diagram for Caplin.DataSource.Publisher.IBroadcastPublisher:

Public Member Functions
void	PublishToPeer (IPeer peer, IMessage message)
	Publishes a message to a specific peer. More...
Public Member Functions inherited from Caplin.DataSource.Publisher.IPublisher
void	PublishInitialMessage (IMessage message)
	Publishes the initial message of the data for a Subject to peers that have just requested (subscribed to) that subject. More...
void	PublishMappingMessage (IMappingMessage mapping)
	Publishes to all peers subscribed to a subject a message that instructs the remote peer to request an alternate subject in order to satisfy the subscription. More...
void	PublishSubjectErrorEvent (ISubjectErrorEvent ev)
	Publishes to all peers subscribed to a subject an event detailing an error in the subscription for that subject. Typically an IDataProvider will use this to notify the remote peers that an string they are subscribed to is no longer available. More...
void	PublishSubjectStatusEvent (ISubjectStatusEvent ev)
	Publishes to all subscribed peers an event about the change in status of a subject. More...
void	PublishToSubscribedPeers (IMessage message)
	Publishes a message to subscribed peers (that is, the peers that have already received an initial image). More...

Additional Inherited Members
Properties inherited from Caplin.DataSource.Publisher.IPublisher
IMessageFactory	MessageFactory [get]
	Gets the IMessageFactory used to create the messages that are published via this publisher. More...

Detailed Description

This implementation of IPublisher sends (broadcasts) updates to all connected peers regardless of whether they have requested (subscribed to) the subject.

Although an Caplin.DataSource.Publisher.IDataProvider can be attached to an IBroadcastPublisher, the IBroadcastPublisher will not invoke any of the IDataProvider's methods.

In general, the use of broadcast messaging is not recommended, because it presents difficulties when handling failover of the DataSource application instance to another instance; the new DataSource instance does not know what data needs to be updated on the DataSource peers. However, broadcast messaging can be useful in situations where messages are transient and the data in them does not need to be always available to peers.

Member Function Documentation

void Caplin.DataSource.Publisher.IBroadcastPublisher.PublishToPeer	(	IPeer	peer,
		IMessage	message
	)

Publishes a message to a specific peer.

Parameters

peer	The peer to publish the message to.
message	The message to be published.