Expand description
UI-agnostic event emission. Consumers — desktop shells, CLI tail
commands, integration tests — implement EventSink and pass it
to crate::Service::build. The engine never touches a UI
framework directly.
Structs§
- Channel
Sink - Fan out via a
tokio::sync::broadcastso multiple subscribers (CLItail, tests) can observe the same stream. - Composed
Sink - Trivial fan-out wrapper so an embedder can plug in more than one sink without writing a custom struct.
- LogSink
- Trace each event through
tracing::info!. Handy default for the headlesspostcratebinary and for tests that just want logs. - Server
Status
Enums§
- Bounce
Kind - Core
Event - Engine event surface. Adding a variant is a semver-minor change —
consumers using
Sink: EventSinkonly have to handle what they know. - Mailbox
State Change
Traits§
- Event
Sink - Implementors receive all engine-level events.