Expand description
The event cache is an abstraction layer, sitting between the Rust SDK and a final client, that acts as a global observer of all the rooms, gathering and inferring some extra useful information about each room. In particular, this doesn’t require subscribing to a specific room to get access to this information.
It’s intended to be fast, robust and easy to maintain, having learned from previous endeavours at implementing middle to high level features elsewhere in the SDK, notably in the UI’s Timeline object.
See the github issue for more details about the historical reasons that led us to start writing this.
Structs§
- Back
Pagination Outcome - The result of a single back-pagination request.
- Event
Cache - An event cache, providing lots of useful functionality for clients.
- Event
Cache Drop Handles - Hold handles to the tasks spawn by a
EventCache. - Room
Event Cache - A subset of an event cache, for a room.
- Room
Event Cache Generic Update - Represents a timeline update of a room. It hides the details of
RoomEventCacheUpdateby being more generic. - Room
Event Cache Subscriber - Thin wrapper for a room event cache subscriber, so as to trigger side-effects when all subscribers are gone.
- Room
Pagination - An API object to run pagination queries on a
super::RoomEventCache. - Thread
Event Cache Update - An update coming from a thread event cache.
Enums§
- Event
Cache Error - An error observed in the
EventCache. - Events
Origin - Indicate where events are coming from.
- Room
Event Cache Update - An update related to events happened in a room.
- Room
Pagination Status - Status for the back-pagination on a room event cache.
Type Aliases§
- Result
- A result using the
EventCacheError.