7cab7cadc9
This modifies the cryptostore and storage logic in two ways:
* The cryptostore trait has only one main save method.
* The receive_sync method tries to save all the objects in one
`save_changes()` call.
This means that all the changes a sync makes get commited to the store
in one transaction, leaving us in a consistent state.
This also means that we can pass the Changes struct the receive sync
method collects to our caller if the caller wishes to store the room
state and crypto state changes in a single transaction.
|
||
|---|---|---|
| .. | ||
| event_emitter | ||
| models | ||
| state | ||
| client.rs | ||
| error.rs | ||
| lib.rs | ||
| session.rs | ||