archive
/
matrix-spec-proposals
mirror of https://github.com/matrix-org/matrix-spec-proposals
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update proposals/4354-sticky-events.md

Browse Source 
Co-authored-by: Travis Ralston <travisr@matrix.org>
kegan/persist-edu
Kegan Dougal 2 months ago committed by GitHub
parent 865746cba5
commit 240d6502cb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File

2
proposals/4354-sticky-events.md
Unescape Escape View File

@ -348,7 +348,7 @@ The `/versions` response in the CSAPI includes:
## Addendum ## Addendum
This section explains how sticky events can be used to implement a short-lived, per-user, per-room key-value store. This section explains how sticky events can be used to implement a short-lived, per-user, per-room key-value store.
This technique would be used by MatrixRTC to synchronise RTC members. This technique would be used by MatrixRTC to synchronise RTC members, and should land in the spec as a suggested algorithm to follow.
### Implementing an ephemeral map ### Implementing an ephemeral map

Write Preview
Loading…
Cancel
Save