forked from mystiq/hydrogen-web
e0d14207ac
as we'll need to await a bogus request first thing after opening the txn funny enough, we originally made it sync to accommodate the same bug in safari, but that didn't prevent any microtask being awaited before scheduling a request in the calling code closing the txn. We'll await a bogus request within the transaction class now so it doesn't depend on the calling code |
||
|---|---|---|
| .. | ||
| megolm | ||
| olm | ||
| Account.js | ||
| attachment.js | ||
| common.js | ||
| DecryptionResult.js | ||
| DeviceTracker.js | ||
| OlmWorker.js | ||
| README.md | ||
| RoomEncryption.js | ||
Integratation within the sync lifetime cycle
session.prepareSync
Decrypt any device messages, and turn them into RoomKey instances. Any rooms that are not in the sync response but for which we receive keys will be included in the rooms to sync.
Runs before any room.prepareSync, so the new room keys can be passed to each room prepareSync to use in decryption.
room.prepareSync
The session can start its own read/write transactions here, rooms only read from a shared transaction
- rooms (with shared read txn)
- megolm decryption read using any new keys decrypted by the session.
room.afterPrepareSync
- rooms
- megolm async decryption
- dispatch to worker
room.writeSync
- rooms (with shared readwrite txn)
- megolm decryption write, yielding decrypted events
- use decrypted events to write room summary
session.writeSync
- writes any room keys that were received
room.afterSync
- rooms
- emit changes
room.afterSyncCompleted
- session
- e2ee account
- generate more otks if needed
- upload new otks if needed or device keys if not uploaded before
- rooms
- share new room keys if needed