synapse-product/synapse/replication/tcp
Erik Johnston 5d3e306d9f
Clean up Notifier.on_new_room_event code path (#8288)
The idea here is that we pass the `max_stream_id` to everything, and only use the stream ID of the particular event to figure out *when* the max stream position has caught up to the event and we can notify people about it.

This is to maintain the distinction between the position of an item in the stream (i.e. event A has stream ID 513) and a token that can be used to partition the stream (i.e. give me all events after stream ID 352). This distinction becomes important when the tokens are more complicated than a single number, which they will be once we start tracking the position of multiple writers in the tokens.

The valid operations here are:

1. Is a position before or after a token
2. Fetching all events between two tokens
3. Merging multiple tokens to get the "max", i.e. `C = max(A, B)` means that for all positions P where P is before A *or* before B, then P is before C.

Future PR will change the token type to a dedicated type.
2020-09-10 13:24:43 +01:00
..
streams Stop sub-classing object (#8249) 2020-09-04 06:54:56 -04:00
__init__.py Fix some spelling mistakes / typos. (#7811) 2020-07-09 09:52:58 -04:00
client.py Clean up Notifier.on_new_room_event code path (#8288) 2020-09-10 13:24:43 +01:00
commands.py Be stricter about JSON that is accepted by Synapse (#8106) 2020-08-19 07:26:03 -04:00
handler.py Revert "Add experimental support for sharding event persister. (#8170)" (#8242) 2020-09-04 10:19:42 +01:00
protocol.py Stop sub-classing object (#8249) 2020-09-04 06:54:56 -04:00
redis.py Handle replication commands synchronously where possible (#7876) 2020-07-27 18:54:43 +01:00
resource.py Stop sub-classing object (#8249) 2020-09-04 06:54:56 -04:00