mirror of https://gitlab.torproject.org/tpo/core/arti http://git.dilluti0n.com/mirrors/arti.git/atom?h=arti-v1.4.0 2021-11-29T11:29:28Z 2021-11-29T11:29:28Z dagon dagon12@tutanota.com 2021-11-29T11:29:28Z urn:sha1:d5c48c616fd40313f0428d14bae97419ae3dac95 2021-11-22T14:39:38Z eta tor@eta.st 2021-11-16T15:21:47Z urn:sha1:98f38dc186212624d377653ed8ecf3c47366c3ad This implements a basic typed event broadcast mechanism, as described in arti#230: consumers of the new `tor-events` crate can emit `TorEvent` events, which others can consume via the `TorEventReceiver`. Under the hood, the crate uses the `async-broadcast` (https://github.com/smol-rs/async-broadcast) crate, and a `futures::mpsc::UnboundedSender` for the event emitters; these are glued together in the `EventReactor`, which must be run in a background thread for things to work. (This is done so event sending is always cheap and non-blocking, since `async-broadcast` senders don't have this functionality.) Additionally, the `TorEventKind` type is used to implement selective event reception / emission: receivers can subscribe to certain event types (and in fact start out receiving nothing), which filters the set of events they receive. Having no subscribers for a given event type means it won't even be emitted in the first place, making things more efficient.