This implementation of IPublisher sends (broadcasts) updates to all connected peers regardless of whether
they have requested (subscribed to) the subject.
Declaration Syntax| C# | Visual Basic | Visual C++ |
public interface IBroadcastPublisher : IPublisher
Public Interface IBroadcastPublisher _ Implements IPublisher
public interface class IBroadcastPublisher : IPublisher
Members| All Members | Methods | Properties | |||
| Icon | Member | Description |
|---|---|---|
 | MessageFactory |
Gets the IMessageFactory used to create the messages that are published via this publisher.
(Inherited from IPublisher.) |
 | PublishInitialMessage(IMessage) |
Publishes the initial message of the data for a Subject
to peers that have just requested (subscribed to) that subject.
(Inherited from IPublisher.) |
| PublishMappingMessage(IMappingMessage) |
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.
(Inherited from IPublisher.) |
| PublishSubjectErrorEvent(ISubjectErrorEvent) |
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.
(Inherited from IPublisher.) |
| PublishSubjectStatusEvent(ISubjectStatusEvent) |
Publishes to all subscribed peers an event about the change in status of a subject.
(Inherited from IPublisher.) |
| PublishToPeer(IPeer, IMessage) |
Publishes a message to a specific peer.
|
| PublishToSubscribedPeers(IMessage) |
Publishes a message to subscribed peers (that is, the peers that have already received an initial image).
(Inherited from IPublisher.) |
RemarksAlthough an 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.