Crates.io | flo_stream |
lib.rs | flo_stream |
version | 0.7.0 |
source | src |
created_at | 2018-08-05 19:24:44.818073 |
updated_at | 2021-11-20 13:25:39.636948 |
description | Pubsub and related streams for Rust futures |
homepage | |
repository | https://github.com/Logicalshift/flo_stream |
max_upload_size | |
id | 77664 |
size | 137,111 |
flo_stream = "0.7"
flo_stream
is a crate providing some extra utilities for streams in Rust's futures
library. The primary new feature
it provides is a "pubsub" mechanism - a way to subscribe to updates sent to a futures Sink
. This differs from the
Sender
/Receiver
mechanism provided in the main futures library in two key ways: it's possible to have multiple
receivers, and messages sent when there is no subscriber connected will be ignored.
The sink type provided is Publisher
. You can create one with let publisher = Publisher::new(10)
. This implements
the Sink
trait so can be used in a very similar way to send messages. The number passed in is the maximum number
of waiting messages allowed for any given subscriber.
A subscription can be created using let subscription = publisher.subscribe()
. Any messages sent to the sink after
this is called is relayed to all subscriptions. A subscription is a Stream
so can interact with other parts of the
futures library in the usual way.
Here's a full worked example with a single subscriber:
let mut publisher = Publisher::new(10);
let mut subscriber = publisher.subscribe();
executor::block_on(async {
publisher.publish(1).await;
publisher.publish(2).await;
publisher.publish(3).await;
assert!(subscriber.next().await == Some(1));
assert!(subscriber.next().await == Some(2));
assert!(subscriber.next().await == Some(3));
});
It's also possible to call subscriber.clone()
to create a new subscription from an existing one without needing to
keep a reference to the publisher. This can be used to reduce the amount of effort needed in passing objects around, and
to hide implementation details from the caller.