Module roopes::prelude::publisher_subscriber

This module implements the Publisher-Subscriber pattern. In this model, a Publisher contains a list of Subscribers. When a message is delivered to the Publisher, it is then delegated directly to all its Subscribers, one at a time. Typically, implementations are dynamic, in that Subscribers are able to be dded or removed at will by the client code - these features are delineated separately in the DetachablePublisher and AttachablePublisher traits, but can be implemented by any Publisher, and together as a MutablePublisher.

![publisher subscriber diagram][publisher-subscriber-diagram]

Modules

• heap
  Provides a heap-based Subscriber which redirects publisher_subscriber::Subscriber::receive calls to a delegate Subscriber.
• prelude
  Exposes the Publisher, Subscriber, AttachablePublisher and DetachablePublisher types at the library level.
• vec_publisher
  Contains an implementation of Publisher which stores its Subscribers in a Vec.

Structs

• VecPublisher
  Implements a Publisher based on a Vec of Subscribers. # Example

Traits

• AttachablePublisher
  Allows Subscribers to be added to the implementing Publisher.
• DetachablePublisher
  Allows Subscribers to be removed from the implementing Publisher.
• MutablePublisher
  Convenience trait for Publishers which implement both AttachablePublisher and DetachablePublisher.
• Publisher
  A Publisher distributes messages it receives to the Subscribers which it currently holds.
• Subscriber
  Subscribers can be attached to, and will receive messages from, Publishers.