Erik Johnston be4a16ff44 Sliding Sync: Track whether we have sent rooms down to clients (#17447) ... The basic idea is that we introduce a new token for a sliding sync connection, which stores the mapping of room to room "status" (i.e. have we sent the room down?). This token allows us to handle duplicate requests properly. In future it can be used to store more "per-connection" information safely. In future this should be migrated into the DB, so its important that we try to reduce the number of syncs where we need to update the per-connection information. In this PoC this only happens when we: a) send down a set of room for the first time, or b) we have previously sent down a room and there are updates but we are not sending the room down the sync (due to not falling in a list range) Co-authored-by: Eric Eastwood <eric.eastwood@beta.gouv.fr>		2024-07-29 22:45:48 +01:00
..
.gitignore
17447.feature	Sliding Sync: Track whether we have sent rooms down to clients (#17447)	2024-07-29 22:45:48 +01:00
17452.misc	Use a new token format for sliding sync (#17452)	2024-07-24 11:47:25 +01:00
17476.doc	Update config_documentation - Change example of msisdn in allowed_local_3pids (#17476)	2024-07-25 11:07:44 +00:00
17477.feature	Sliding Sync: Add Account Data extension (MSC3959) (#17477)	2024-07-24 17:10:38 -05:00
17478.misc	Sliding Sync: ensure bump stamp ignores backfilled events (#17478)	2024-07-24 15:21:56 +01:00
17481.misc	Refactor Sliding Sync tests to better utilize the SlidingSyncBase (pt. 1) (#17481)	2024-07-25 10:43:35 -05:00
17482.misc	Refactor Sliding Sync tests to better utilize the SlidingSyncBase.do_sync(...) (pt. 2) (#17482)	2024-07-25 11:01:47 -05:00