Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

change handling of multiple olm sessions according to spec #705

Open
uhoreg opened this issue Aug 30, 2018 · 1 comment
Open

change handling of multiple olm sessions according to spec #705

uhoreg opened this issue Aug 30, 2018 · 1 comment
Labels
T-Defect

Comments

@uhoreg
Copy link
Member

uhoreg commented Aug 30, 2018

The current behaviour uses the session with the lowest ID. The new spec (matrix-org/matrix-spec-proposals#1596) uses the session that the client last received a message on, and expires old sessions.
@uhoreg
Copy link
Member Author

uhoreg commented Sep 7, 2018

This would require modifying getSessionIdForDevice in src/crypto/OlmDevice.js, and probably will need to store the time that the client last received a mesage for each session in indexedDB

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
T-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@uhoreg @turt2live