[E2E] Megolm inbound sessions #241
Conversation
|
@non-Jedi what do you think of 5f79968? This makes the decryption process totally transparent to SDK users (which is not very good when you want to tell them that an event is verified or not, but it will stay that way in this PR). edit: well, it definitely is too transparent and should be changed in this PR, since an application is quite likely to need to know if a message was encrypted or not (as it cannot infer that a message was encrypted from the fact that it received it from an encrypted room, since messages can be always be sent unencrypted). |
Use a thread to allow downloading the keys in a non-blocking way. Implement sort of a queue of users who need updating, which should be efficient (request is fired as soon as possible with as much data as possible) and avoid races (we always have only one download in progress).
This has the effect of tracking the device lists of users proactively.
2 participants
Just one more to go!
Signed-off-by: Valentin Deniaud <valentin.deniaud@inpt.fr>